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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered by structured data. The description contributes the ownership authorization requirement, which is genuinely supplemental. It does not disclose whether the delete is hard or soft, or what happens to invoices and payments still linked to the client — a material gap for a destructive operation.

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?

A single front-loaded sentence with no filler. It is perhaps too terse for a destructive operation, but nothing is wasted or buried.

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?

Annotations plus the fully documented single parameter mean an agent can technically invoke this correctly. For a destructive, irreversible-sounding tool, though, the description should mention cascading effects on related invoices or that the record must be owned/verified first; that absence leaves the most consequential behavior unstated.

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% for the single required 'id' parameter, so baseline 3 applies. The description adds no format hints or notes about how to obtain a valid id.

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 (delete) and resource (invoice_client), which cleanly separates it from invoice_client_read, invoice_client_update, and invoice_client_search siblings. The 'you own' qualifier narrows the scope further. Minor grammar slip ('a invoice_client') is cosmetic only.

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?

No statement of when to use this versus the sibling lifecycle tools (invoice_client_update, invoice_client_upsert, or even invoice_client_read first to confirm identity). The ownership restriction is implied as a gate but no preconditions are spelled out, and there is no guidance on irreversible consequences or confirming before deletion.

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