Should output also have a schema?

[bokand]

The explainer includes an example returning some structured output:

return {
        content: [
            {
                type: "text",
                text: `Stamp "${name}" added successfully! The collection now contains ${stamps.length} stamps.`, 
            },
        ]
    };

Should we include an outputSchema as MCP recently added?

I'm not sure the schema itself helps (the return is already a JavaScript object...) but descriptions might help the agent understand what the output means?

[bwalderman]

The motivation for outputSchema in MCP is discussed here modelcontextprotocol/modelcontextprotocol#356

Seems like if it makes sense for classic MCP, it would make sense for WebMCP too.