Storyblok MCP Server

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

No annotations are provided, so the description carries full burden. It states this is a deletion operation, implying it's destructive, but doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, what permissions are required, if there are rate limits, or what happens to associated data. For a destructive tool with zero annotation coverage, this is inadequate.

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 a single, clear sentence with no wasted words. It's appropriately sized for a simple tool, though it could be more front-loaded with critical details like the parameter. There's no fluff, making it efficient.

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 destructive tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks essential context: parameter explanation, behavioral details (permissions, reversibility), and output expectations. Given the complexity of a deletion operation in a content management system, this leaves significant gaps for an agent.

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?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description doesn't mention the 'datasource_entry_id' parameter at all, nor does it explain what this ID represents or how to obtain it. However, with only 1 parameter and no schema descriptions, the baseline is 3 as the description doesn't compensate for the lack of parameter documentation.

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 clearly states the action ('Deletes') and target ('a datasource entry'), and specifies the context ('from a specified Storyblok space using the Management API'). It distinguishes itself from generic deletion tools by naming the specific resource type. However, it doesn't explicitly differentiate from sibling deletion tools like 'delete_datasource' or 'delete_story', which would require a 5.

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 doesn't mention prerequisites (e.g., needing a datasource entry ID), when not to use it (e.g., for bulk deletion), or refer to sibling tools like 'delete_datasource' or 'bulk_delete_stories'. Without any usage context, this is minimal guidance.

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