Scenario.com MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description fails to specify critical details such as whether deletion is permanent or reversible, what permissions are required, if there are side effects (e.g., cascading deletion of contained items), or rate limits. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with a single sentence 'Delete a collection', which is front-loaded and wastes no words. It directly states the action, making it efficient and easy to parse, though this brevity contributes to gaps in other dimensions.

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?

Given the tool's complexity as a destructive operation with no annotations and no output schema, the description is incomplete. It does not cover behavioral aspects like permanence, permissions, or effects, nor does it explain return values or error conditions. For a deletion tool, this lack of context is a significant shortfall.

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 input schema has 100% description coverage, with the single parameter 'collectionId' documented as 'The collection ID to delete'. The description adds no additional parameter information, but with high schema coverage and only one parameter, the baseline is elevated. The description does not compensate for any gaps, but none exist, so it meets expectations without adding value.

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 'Delete a collection' clearly states the verb ('Delete') and resource ('a collection'), providing a basic purpose. However, it lacks specificity about what a 'collection' represents in this context (e.g., a set of assets, models, or workflows) and does not differentiate from sibling deletion tools like 'delete-assets-by-collection-id' or 'delete-models-by-collection-id', making it vague in comparison.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., whether the collection must be empty), exclusions (e.g., cannot delete system collections), or refer to sibling tools for related operations, leaving usage entirely implicit based on the tool name alone.

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