delete_transfer

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

Adds that the operation is irreversible and requires user confirmation, which goes beyond the destructiveHint annotation. Provides important behavioral context 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?

Extremely concise with a warning emoji and two key points: action and confirmation requirement. No unnecessary words.

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?

Adequate for a simple one-parameter delete tool with output schema present, but does not mention any side effects or cascading deletions. Could be more complete.

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 0% and description provides no information about the transfer_id parameter. Agent receives no guidance on what to provide beyond the schema.

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?

Description clearly states the verb 'Elimina' (delete), resource 'traspaso' (transfer), and emphasizes irreversibility. It distinguishes from sibling delete tools by specifying 'transfer'.

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?

Includes instruction to confirm with user, implying when to use, but does not explicitly state when not to use or mention alternative tools. Guidelines are minimal but present.

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