Storyblok MCP Server

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

With no annotations provided, the description carries full burden. It states the tool performs a deletion but doesn't disclose critical behavioral traits: whether it's destructive (implied but not explicit), requires specific permissions, has rate limits, or what happens to associated data. This leaves significant gaps for a 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 efficiently structured: a clear opening sentence followed by a bullet point for the parameter. Every element serves a purpose with zero wasted words, making it easy to parse 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 mutation tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks information on permissions, side effects, error conditions, or return values, which are essential for safe and effective use.

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%, but the description adds the parameter 'branch_id' with a brief explanation ('Numeric ID of the branch to delete'). This provides basic semantics beyond the schema's type-only definition, though it doesn't fully compensate for the coverage gap (e.g., no format examples or constraints).

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 resource ('a branch (pipeline) by its ID in a Storyblok space'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_space' 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., branch must exist, user permissions), consequences (e.g., irreversible deletion), or related tools like 'retrieve_single_branch' for verification.

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