Storyblok MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'permanently deletes,' which implies a destructive, irreversible action, but doesn't cover critical aspects like required permissions, confirmation prompts, rate limits, or what happens to associated data (e.g., stories, assets). This is a significant gap for a high-risk mutation tool.

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 wasted words. It's front-loaded with the key action ('permanently deletes') and resource, making it easy to scan and understand quickly.

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, no output schema, and low schema coverage, the description is inadequate. It lacks details on permissions, consequences, error handling, and return values, leaving the agent with insufficient context to use it safely and 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 schema has 0% description coverage, but the description doesn't add any parameter details beyond what the schema implies (a 'space_id' is needed). It doesn't explain what a space ID is, how to obtain it, or format constraints. With one parameter, the baseline is 4, but the lack of compensation for the coverage gap lowers it to 3.

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 ('permanently deletes') and resource ('a Storyblok space'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_story' or 'delete_asset', 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 (e.g., 'delete_story' for individual stories or 'duplicate_space' for copying). It mentions the Management API but doesn't specify prerequisites, permissions, or typical scenarios for space deletion.

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