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 mentions using the 'Management API' which hints at administrative access, but doesn't disclose critical behavioral traits like required permissions, whether this is a mutation (likely yes), rate limits, or what happens on success/failure. For a tool that likely creates resources, 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's appropriately sized and front-loaded with the core action. Every word earns its place.

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 6 parameters with 0% schema coverage, no annotations, no output schema, and complexity of creating a webhook, the description is incomplete. It doesn't explain parameter meanings, behavioral expectations, or return values. The mention of 'Management API' adds some context but insufficient for proper tool usage.

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 description must compensate for all 6 parameters. It adds no information about parameters beyond implying a 'specified Storyblok space' (which isn't even a parameter in the schema). The description doesn't explain what 'actions', 'endpoint', 'name', etc. mean or how they're used.

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 ('Adds a new webhook') and the target resource ('to a specified Storyblok space'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'update_webhook' or 'delete_webhook' beyond the basic action difference, which keeps it from 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?

The description provides no guidance on when to use this tool versus alternatives like 'update_webhook' or 'delete_webhook', nor does it mention prerequisites such as needing a space ID or Management API access. It only states what the tool does, not when to use it.

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