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 of behavioral disclosure. While 'Publishes' implies a write operation, it doesn't specify whether this is destructive, requires specific permissions, has side effects (e.g., triggering webhooks), or what happens on failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 core action without 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 the complexity of a publish operation (a mutation with potential side effects), no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It should explain behavioral traits, parameter purposes, and expected outcomes to be complete for this 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 0%, meaning none of the three parameters (story_id, lang, release_id) are documented in the schema. The description only mentions 'by its ID', which partially explains the required 'story_id' parameter but ignores the optional 'lang' and 'release_id' parameters. It adds minimal value beyond the schema.

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 verb ('Publishes') and resource ('a Storyblok story by its ID'), making the purpose specific and understandable. However, it doesn't distinguish this tool from sibling tools like 'bulk_publish_stories' or 'unpublish_story', which would require explicit differentiation to achieve 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 provides no guidance on when to use this tool versus alternatives like 'bulk_publish_stories' or 'unpublish_story'. It also lacks information about prerequisites (e.g., whether the story must be in a draft state) or contextual constraints, leaving the agent without usage direction.

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