fusion_delete_body

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

The description repeats 'Destructive,' which is already indicated by the destructiveHint annotation (true). It adds no new behavioral context beyond what the annotation provides, such as whether deletion is reversible or cascades to child entities.

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 extremely concise with no wasted words. However, it could be slightly more informative without losing conciseness (e.g., mentioning the parameter type). Still, it's appropriately sized for a simple operation.

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 operation with one parameter and no output schema, the description lacks essential context such as return value, undoability, or prerequisites (e.g., body existence). The brevity leaves the agent with insufficient information to use the tool confidently.

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 single parameter 'body' has no description in the schema (0% coverage). The description merely says 'Delete a body' without clarifying what the parameter expects (e.g., body ID, name) or any constraints. This fails to compensate for the 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 action ('Delete') and the resource ('a body'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like fusion_rename_body or fusion_move_body by focusing on deletion.

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 only says 'Destructive,' which implies when to use it but provides no explicit guidance on when not to use it or alternatives (e.g., fusion_delete_all for clearing everything). No context about prerequisites or consequences.

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