mark_invoice_sent

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

The description does not disclose any behavioral traits beyond the basic action. Annotations are absent, so the description should explain side effects (e.g., does it send an email?), idempotency, permission needs, or state changes, but it fails to do so.

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 extremely concise (one short sentence), but this brevity comes at the cost of essential information. It is not wordy, but it under-delivers for the agent's needs.

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?

Given the presence of an output schema (not shown) and a single parameter, the description is incomplete. It omits return value details, error states, and any explanation of the 'sent' status, making it insufficient for reliable use.

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?

With 0% schema description coverage and a single parameter (invoice_id), the description adds no meaning beyond the schema. The agent gains no insight into how to obtain or format the invoice_id, or any constraints.

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 clearly states the action 'Mark an invoice as sent,' with a specific verb and resource. This distinguishes it from sibling tools like approve_invoice or finalize_invoice, as it uniquely indicates a status change to 'sent.'

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 guidance is provided on when to use this tool versus alternatives, such as approve_invoice or finalize_invoice. There is no mention of prerequisites, restrictions, or context, leaving the agent without decision support.

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