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 but only mentions optional publishing. It doesn't disclose critical behavioral traits like required permissions, whether updates are atomic or batched, error handling for partial failures, rate limits, or what the response looks like (no output schema). This is inadequate 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 zero waste. It's front-loaded with the core purpose and includes a useful qualifier about optional publishing, making it appropriately sized for its content.

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 bulk mutation tool with no annotations and no output schema, the description is incomplete. It lacks necessary context about permissions, error handling, response format, and differentiation from siblings. The high schema coverage doesn't compensate for these behavioral gaps.

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 'stories' array and its nested properties well-documented in the schema. The description adds no parameter semantics beyond what the schema provides, such as explaining field interactions or constraints. Baseline 3 is appropriate given the schema does the heavy lifting.

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 ('Updates multiple stories') and resource ('in Storyblok'), which is specific and distinguishes it from single-story operations like 'update_story'. However, it doesn't explicitly differentiate from sibling 'bulk_publish_stories' or 'bulk_create_stories' beyond the optional publishing mention.

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_story' (for single updates) or 'bulk_publish_stories' (for publishing only). It mentions optional publishing but doesn't clarify trade-offs or prerequisites for bulk operations.

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