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 but only states it's a deletion via an API. It doesn't disclose behavioral traits like whether the deletion is permanent, requires specific permissions, has side effects (e.g., on scheduled stories), or error handling, which is inadequate for a destructive operation.

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, front-loaded with the core action. It's appropriately sized for a simple tool, though brevity contributes to gaps in other dimensions.

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 tool's destructive nature, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks critical context like behavioral risks, parameter guidance, and usage scenarios, making it insufficient for safe and effective agent use.

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%, but the description adds no parameter details beyond what the schema implies. It mentions 'story schedule entry' which aligns with the 'story_scheduling_id' parameter, but doesn't explain its format, source, or constraints. With 1 parameter and low coverage, this is a minimal baseline.

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 ('Deletes') and resource ('a story schedule entry'), specifying it operates via the Storyblok Management API. It distinguishes from siblings like 'delete_story' or 'bulk_delete_stories' by targeting schedule entries, but doesn't explicitly contrast with 'retrieve_one_story_schedule' or 'retrieve_multiple_story_schedules' for context.

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. It doesn't mention prerequisites (e.g., needing an existing schedule ID), exclusions, or sibling tools like 'update_story_schedule' or 'create_story_schedule' for related operations, leaving usage context unclear.

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