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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds genuine value by specifying what is destroyed (the transfer and its timeline), that the action is irreversible, and that re-adding the UETR later creates a fresh transfer. It doesn't cover secondary effects such as webhook deliveries or watcher state tied to the deleted transfer.

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?

Three short sentences, front-loaded with the action and its permanence, then the alternative, then the recreation consequence. Every sentence contributes a distinct fact with no filler or repetition of the title.

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 single-identifier destructive tool with rich annotations and an existing output schema, the definition covers what the agent needs: irreversibility, the archive alternative, and the post-delete recreation behavior. Nothing essential to correct invocation is missing.

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?

Only one parameter (uetr) exists and schema description coverage is 100%, with the pattern already constraining format in the schema. The description adds no additional semantics about the identifier beyond implying it selects the transfer to delete, so the baseline of 3 applies.

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?

States a specific verb and resource ("Permanently delete a transfer") plus the scope detail that it applies whether the transfer is archived or not, and that the timeline goes with it. This clearly distinguishes it from sibling operations like archive_transfer, restore_transfer, or remove_team_member.

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?

It gives a clear when-not signal by contrasting deletion with archiving ("archiving keeps the transfer instead"), which implicitly routes the agent to the archive_transfer sibling. It stops short of explicitly naming that sibling tool or stating any preconditions the caller must confirm first.

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