delete_entity

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

Annotations already mark destructiveHint=true, but the description adds valuable context: the need for explicit confirmation and the refusal of recursive deletion. This goes beyond the annotation by explaining the safety mechanism and the boundary of what is allowed.

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?

Two sentences with zero filler. The action is front-loaded, and the safety constraint follows immediately. Every word earns its place.

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 two-parameter deletion tool, the description covers the essential behaviors: what it deletes, the confirmation requirement, and the recursive-deletion limitation. It doesn't discuss error handling or return values, but the absence of an output schema and the tool's simplicity make this acceptable.

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 explicitly mentions 'requires explicit confirmation', which explains the purpose of the 'confirm' parameter. However, it provides no detail about the 'path' parameter beyond 'file or folder' – no format, examples, or constraints beyond the schema's minLength. With schema coverage at 0%, the description partially compensates but doesn't fully clarify both parameters.

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 it deletes a file or folder, which is a specific verb and resource. It distinguishes itself from sibling tools like rename_entity, create_file, and upload_file by focusing exclusively 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 gives practical usage constraints: it requires explicit confirmation (implying the 'confirm' parameter must be set to true) and refuses recursive folder deletion. While it doesn't name alternative tools explicitly, the deletion use case is self-evident and the constraints are clearly stated.

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