delete_space

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

Adds owner constraint beyond annotations (destructiveHint=true), but does not disclose irreversibility, cascading effects, or what happens to contained data. Missing behavioral details important for a destructive action.

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?

Short and front-loaded with action and constraint. Efficient two-sentence description plus args/returns. Slight lack of structured format but overall concise.

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?

Omits critical context such as irreversibility, data loss, and prerequisites for deletion. Given the destructive nature and simple schema, description should clarify that the operation permanently removes the space and all its contents.

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?

With 0% schema description coverage, description merely restates the parameter name as 'The space ID to delete', adding no format, constraints, or examples. Insufficient compensation for missing schema documentation.

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 'Delete' and the resource 'context space', and adds an ownership constraint. It distinguishes from siblings like create_space, update_space, and share_space.

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?

Mentions 'owner only' implying who should use it, but lacks explicit guidance on when to use versus alternatives, prerequisites, or conditions like checking if space exists.

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