Storyblok MCP Server

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states the action is destructive ('Deletes'), but doesn't cover critical aspects like irreversibility, permissions required, rate limits, error handling, or what constitutes a valid ID. This is inadequate for a mutation tool.

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 front-loads the core action and resource, making it easy to scan. Every element ('Deletes multiple assets', 'by numeric IDs', 'using the Storyblok Management API') contributes essential information.

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 destructive mutation tool with no annotations, 0% schema coverage, and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., permanence, auth needs), parameter constraints, error responses, and usage context, leaving the agent under-informed.

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 some value by specifying 'numeric IDs' for the 'ids' parameter, clarifying the data type beyond the schema's 'integer' array. However, it doesn't explain constraints (e.g., max array size, valid ID ranges) or provide examples, leaving gaps.

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 ('multiple assets'), specifying they are identified by 'numeric IDs' and using the 'Storyblok Management API'. It distinguishes from the sibling 'delete_asset' by handling multiple assets, but doesn't explicitly contrast with other bulk operations like 'bulk_delete_stories'.

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., permissions), compare with single-asset deletion ('delete_asset') or other bulk operations, or specify scenarios where it's appropriate (e.g., batch cleanup).

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