Storyblok 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. It states 'permanently deletes,' which implies a destructive, irreversible action, but fails to mention critical details like required permissions, confirmation steps, rate limits, or error handling. For a high-impact mutation tool, this is a significant gap.

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, efficient sentence with zero waste—it directly states the action, resource, and API context without unnecessary words. It is front-loaded and appropriately sized for the tool's purpose.

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 high complexity (destructive deletion) and lack of annotations or output schema, the description is incomplete. It does not address behavioral aspects like permissions, confirmation, or error handling, which are crucial for safe usage. The description alone is insufficient for an agent to invoke this tool responsibly.

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 100%, with the single parameter 'space_id' documented as 'ID of the space to delete.' The description does not add any additional meaning beyond this, such as format examples or sourcing tips. The baseline score of 3 is appropriate since the schema adequately covers the parameter.

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 specific action ('permanently deletes') and resource ('a Storyblok space'), distinguishing it from sibling tools like 'delete_story' or 'delete_asset' by specifying the exact resource type. It also mentions the API context ('using the Management API'), which adds precision.

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, such as 'delete_story' or 'duplicate_space', nor does it mention prerequisites like permissions or confirmations. It lacks explicit usage context or exclusions, leaving the agent to infer based on the name alone.

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