Storyblok MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data, implying it's a read operation, but doesn't mention potential side effects, error handling, rate limits, or authentication requirements. This leaves significant gaps in understanding how the tool behaves in practice.

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, straightforward sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly, though it could be more informative without sacrificing brevity.

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 retrieval tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, return values, error conditions, and usage context, making it inadequate for an agent to use the tool effectively without additional guesswork.

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 schema only provides a parameter name and type without meaning. The description adds no information about the 'datasource_entry_id' parameter, such as what it represents, where to find it, or valid ranges. This fails to compensate for the low schema coverage.

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 verb 'retrieves' and resource 'a single datasource entry', which clarifies the basic action. However, it doesn't distinguish this tool from sibling tools like 'retrieve_multiple_datasource_entries' or 'get_story', leaving the scope vague regarding what makes this retrieval specific to datasource entries versus other resources.

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. The description mentions the Storyblok Management API but doesn't specify prerequisites, such as authentication or permissions, or differentiate it from similar tools like 'retrieve_single_datasource' or 'retrieve_multiple_datasource_entries'.

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