Scenario.com MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full responsibility for behavioral disclosure but offers none. 'Create workflow' implies a write/mutation operation but doesn't specify permissions required, whether the operation is idempotent, what happens on conflict, rate limits, or what the response contains. For a creation tool with zero annotation coverage, this leaves critical behavioral aspects completely undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is maximally concise at two words, with no wasted language. While severely under-specified, it's not verbose or poorly structured—it simply provides the absolute minimum information possible. Every word ('Create workflow') directly relates to the tool's function, earning its place despite the overall inadequacy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 2 required parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what a workflow is, what the parameters mean, what happens during creation, what gets returned, or how this differs from related operations. The agent lacks sufficient context to use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides zero information about parameters, while the input schema has 0% description coverage (no parameter descriptions in schema). With 2 required parameters (name, description) completely undocumented in both schema and description, the agent has no semantic understanding of what these parameters represent, their format constraints, or how they affect workflow creation. This fails to compensate for the schema's documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create workflow' is a tautology that essentially restates the tool name 'post-workflows' without adding meaningful specificity. It doesn't clarify what a 'workflow' is in this context, what resources are involved, or how this differs from sibling tools like 'put-workflows-by-workflow-id' (which likely updates existing workflows). While the verb 'Create' is clear, the object 'workflow' remains undefined and indistinguishable from related operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or when to choose this over sibling tools like 'put-workflows-by-workflow-id' (for updates) or 'get-workflows' (for retrieval). The agent receives no directional information about application scenarios or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.