delete_drive

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

Description adds context that deletion is permanent (not archive/trash), which aligns with destructiveHint=true. Also discloses error behavior for non-empty drives, going beyond annotations.

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 no filler. Every sentence provides value: action, precondition, and permanence.

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?

Complete description for a deletion tool with destructiveHint=true. Covers precondition, permanence, and error behavior. Output schema exists to handle rest.

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?

Schema coverage is 100% and description adds minimal info beyond the schema ('a string that will be trimmed'). Baseline of 3 is appropriate as schema does the heavy lifting.

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 'Permanently delete an empty Huly Drive space' with specific verb and resource, and distinguishes from archive or trash operations. It also clarifies the empty precondition.

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?

Explicitly states the Drive must be empty and describes failure for non-empty Drives. Provides clear when-to-use guidance, though no alternative tools are named.

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