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

Annotations already declare destructiveHint=true, and the description reinforces that, adding the explicit confirmation requirement and stating the side effect directly. This gives useful behavioral context beyond what the annotation alone provides, though some of it duplicates schema fields.

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 short and front-loaded with the core action. The 'Side effects' sentence is somewhat redundant with the first sentence, but the overall size is appropriate and easy to parse.

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?

The tool is a simple destructive delete with a complete input schema, an output schema, and annotations that already mark it destructive. The description covers the essential safety requirement and side effect, making it sufficient without needing extensive additional detail.

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 description coverage is 100%, so the schema fully describes outbox_fax_id, confirmation_text, and user_id. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 names a specific verb ('Delete a queued outbox fax record') and identifies the exact resource being acted on. It stands apart from sibling delete-fax by explicitly saying 'outbox fax', so an agent can distinguish the target without opening the schema.

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 no explicit when-to-use guidance, exclusions, or alternatives among siblings such as delete-fax, bulk-update-outbox-faxes, or get-outbox-fax. It mostly restates the action rather than explaining the conditions for choosing this tool over siblings.

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