accept invoice change

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. The description adds real value beyond them by enumerating the mutation types (add a line, change a rate, apply a discount, move the due date) and the human-approval precondition. It does not state reversibility or error behavior, keeping it short of a 5.

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?

Front-loaded with the core action, then the precondition. Three sentences with only mild redundancy — the closing sentence re-emphasizes approval already stated in sentence one, which is defensible as a guardrail but slightly repetitive.

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?

Output schema exists, so return values need no explanation, and annotations carry the safety/idempotency profile. The description supplies the approval prerequisite and the range of possible mutations, leaving only per-parameter detail for changeId/invoiceId as a minor gap.

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 0% across 3 parameters, so the description must compensate. It does explain the critical one ('confirmed' must be true, only after approval), but changeId and invoiceId are left entirely to their names. Partial compensation only.

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 ('Apply') and resource ('one suggested invoice change') with clear scope, and implicitly contrasts with the sibling suggest_invoice_change by specifying this is the accepting/committing half of the workflow. An agent can distinguish it from the suggest path 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?

Gives an explicit condition for use ('after the freelancer explicitly approves that change', 'Pass confirmed true only then') and a negative guard ('not a substitute for the freelancer's approval'). It does not name a sibling alternative explicitly, but the gating condition is unambiguous.

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