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 'adds a collaborator' but does not clarify if this is a mutating operation, what permissions are needed, how errors are handled, or what the output looks like. It lacks essential context for safe and effective use.

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 brief and front-loaded with the purpose, followed by parameter guidance. Both sentences are necessary, with no redundant information, though it could be slightly more structured for clarity.

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 mutation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It covers parameter usage but omits behavioral traits, error handling, and output details, leaving critical gaps for agent understanding.

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 significant value by explaining the exclusive usage of 'role', 'space_role_id', or 'space_role_ids', which clarifies parameter relationships not evident in the schema (0% coverage). However, it does not explain other parameters like 'allow_multiple_roles_creation' or 'permissions', leaving some 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 verb 'adds' and the resource 'collaborator to a space in Storyblok', specifying the exact action and target. It distinguishes from siblings like 'delete_collaborator' and 'update_collaborator' by focusing on creation rather than removal or modification.

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, such as 'create_space_role' or 'update_collaborator', nor does it mention prerequisites like required permissions or existing space context. It only includes parameter usage rules, not tool selection advice.

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