delete_space

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

The description discloses the permanent nature of the deletion ('permanently deletes'), which is a key behavioral trait. However, with no annotations provided, it lacks details on side effects, required permissions, or whether the action is reversible. The transparency is adequate but not comprehensive.

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 sentence that is direct and front-loaded with the key action. Every word is purposeful, with no extraneous information. It is highly concise and well-structured.

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 simple deletion tool with one parameter and no output schema, the description is largely complete. It covers the core action and permanence. However, it could be enhanced with a brief note on irreversibility or confirmation steps, but overall it is sufficient.

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 input schema has 100% description coverage for the single parameter ('space_id'), so the schema itself provides clear meaning. The description adds no additional semantic value beyond what the schema already conveys, meeting the baseline expectation.

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 'deletes', the resource 'Storyblok space', and the method 'Management API'. It explicitly mentions permanence, which distinguishes it from other deletion tools like 'delete_story' or 'delete_space_role'. The action and scope are unambiguous.

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 prerequisites, consequences, or context. It does not mention any conditions or warnings, leaving the agent to infer usage without support.

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