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. 'Deletes' implies a destructive mutation, but it fails to disclose critical behavioral traits like whether deletion is permanent or reversible, what permissions are required, if it affects related resources, or what the response looks like. This is inadequate for a destructive 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, direct sentence with zero wasted words. It's front-loaded and appropriately sized for a simple tool, making it highly efficient and easy to parse.

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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address safety, permissions, or behavioral outcomes, leaving significant gaps for an agent to understand the tool's impact and usage context.

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 parameter 'release_id' fully documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or constraints, but meets the baseline since the schema handles parameter documentation effectively.

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 'Deletes a release' clearly states the verb ('deletes') and resource ('a release'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_story' or 'delete_asset' by specifying what type of release this is or its scope, preventing a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling deletion tools (e.g., delete_story, delete_asset, delete_space), the description lacks context about prerequisites, permissions, or typical use cases, leaving the agent to infer usage.

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