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. It mentions 'Triggers a backup task' but does not disclose behavioral traits such as whether this is asynchronous, requires specific permissions, has rate limits, or what the expected outcome is (e.g., backup file location). 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 a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary details.

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 complexity of a backup operation (a mutation tool with no annotations, no output schema, and low schema coverage), the description is incomplete. It lacks details on behavior, output, error handling, and usage context, making it inadequate for safe and effective tool invocation.

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 description does not add any meaning beyond the input schema, which has 0% description coverage for the single parameter 'space_id'. Since schema coverage is low, the description should compensate but does not, resulting in a baseline score of 3 due to the minimal parameter count (1).

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 states the tool 'Triggers a backup task for a Storyblok space using Management API,' which provides a clear verb ('Triggers') and resource ('backup task for a Storyblok space'). However, it does not differentiate from sibling tools like 'duplicate_space' or specify what 'backup' entails (e.g., data export vs. snapshot), making it somewhat vague.

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. It does not mention prerequisites (e.g., space must exist), timing considerations, or related tools like 'duplicate_space' for similar operations, leaving usage context unclear.

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