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

With no annotations, the description carries the full burden and it does disclose some behavior: an outbound email is sent from the firm's own inbox, delivered immediately, and worded politely. It omits material traits for an irreversible outbound-communication tool — whether the message is idempotent on repeat calls, whether approval is required, what the email contains, and whether the action is logged or reversible.

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 short sentence that front-loads the action and packs in the overdue precondition, the immediacy, the tone, and the sending identity with no filler. Every word carries information.

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 one-parameter tool with no output schema, the description covers the action adequately. It still leaves open what the caller gets back — confirmation that the email was sent, failure behavior, or what happens if the invoice is not actually overdue — which matters more here because the tool performs an irreversible external send.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents invoice_id and a baseline of 3 applies. The description adds only the implicit constraint that the id should refer to an overdue invoice, and nothing about format or where to obtain the 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?

The description names a specific verb (chase) and resource (an overdue invoice) plus the channel (from the firm's inbox), so an agent can tell this is a payment-reminder send rather than a document resend. It does not contrast itself with plausible siblings such as send_invoice or list_invoices, leaving that distinction to inference.

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?

"Overdue invoice" and "now" imply a precondition (the invoice must already be past due) and immediacy, which is useful context for when to call. However, there is no explicit statement of when NOT to use it, no named alternative for non-overdue invoices, and no guidance on repeated chasing.

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