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 for behavioral disclosure. While 'Creates' implies a write/mutation operation, it doesn't specify permissions required, whether this is an atomic transaction, rate limits, error handling for partial failures, or what happens on success. For a bulk write tool with zero annotation coverage, this leaves significant gaps.

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 that communicates the core purpose without any wasted words. It's appropriately sized for a tool with a straightforward purpose and good schema documentation.

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 write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes a valid story object beyond the schema, how many stories can be created in one call, whether there are size limits, what the return value looks like, or error scenarios. The combination of mutation behavior and lack of structured documentation requires more descriptive 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 single parameter 'stories' clearly documented as 'Array of story objects to create'. The description adds no additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate when schema documentation is complete.

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 ('Creates') and resource ('multiple stories in Storyblok'), making the purpose immediately understandable. It distinguishes from the sibling 'create_story' by specifying bulk/multiple creation, though it doesn't explicitly contrast with other bulk operations like 'bulk_update_stories' or 'bulk_delete_stories'.

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. It doesn't mention when bulk creation is preferable to individual creation with 'create_story', nor does it address prerequisites, limitations, or appropriate contexts for bulk operations.

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