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. It only states what the tool does ('fetch') without any information about permissions required, rate limits, whether it's read-only or has side effects, error behavior, or return format. This is inadequate for a tool with 30 parameters.

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, well-structured sentence that efficiently communicates the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.

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 high complexity (30 parameters, no schema descriptions, no annotations, no output schema), the description is severely incomplete. It doesn't explain what 'stories' are in Storyblok context, how filtering works, what pagination returns, or any behavioral aspects needed for proper tool selection and 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?

Schema description coverage is 0% (all parameters have only titles like 'By Ids'), and the description provides no parameter information beyond 'advanced filtering and pagination'. With 30 undocumented parameters, the description fails to compensate for the complete lack of schema documentation.

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 ('fetch') and resource ('stories from Storyblok'), and specifies 'multiple stories' to indicate bulk retrieval. However, it doesn't differentiate from sibling tools like 'get_story' (singular) or 'bulk_create_stories' (write operation), which would require explicit comparison for 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 mentions 'advanced filtering and pagination' which implies usage for complex queries, but provides no explicit guidance on when to use this tool versus alternatives like 'get_story' (singular fetch) or 'bulk_create_stories' (write operation). There are no when/when-not statements or named alternatives.

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