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 states it's a retrieval operation but doesn't mention whether it's read-only, what permissions are needed, error handling, or response format. This leaves significant gaps for a tool with no annotation coverage.

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 appropriately brief with two sentences that get straight to the point. The bullet point format for the parameter is efficient. However, the second sentence could be integrated more smoothly rather than as a separate bullet.

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 retrieval tool with no annotations, no output schema, and minimal parameter documentation, the description is inadequate. It should explain what information is returned, error conditions, authentication requirements, and how this differs from similar retrieval tools in the sibling list.

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?

The description adds the parameter 'discussion_id' with a brief explanation ('Numeric ID of the discussion'), which provides basic semantics. However, with 0% schema description coverage and only one parameter documented, this is the minimum viable baseline - it adds some value but doesn't fully compensate for the schema's lack of descriptions.

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 ('retrieves') and resource ('a specific discussion by its ID in a Storyblok space'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'retrieve_multiple_discussions' or 'retrieve_my_discussions', which would require a 5.

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 like 'retrieve_multiple_discussions' or 'retrieve_my_discussions'. The description only states what it does, not when it's appropriate or what prerequisites might exist.

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