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

Goes well beyond the annotations (readOnly/openWorld/non-destructive) by disclosing the state transitions, the Balanced-invoice gate, background execution, that the call returns status on completion, that per-call confirmation applies, that other people are reached, and that a Cotlet API key with app access is required.

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 effects of release are stated twice: 'becomes Open, raises the customer balance and creates a ledger batch' is repeated almost verbatim as 'makes the invoice Open, increases the customer balance and generates a general ledger batch.' Otherwise front-loaded and readable.

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 two-parameter mutation with no output schema, the description covers prerequisites, side effects, execution mode, confirmation policy, and auth requirements. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it ties remove_hold to the On Hold state rather than just restating 'removes the hold.' reference_nbr is left to the schema.

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 (Release) and resource (one AR invoice) and spells out the three effects (becomes Open, raises customer balance, creates a ledger batch). An agent can distinguish it from acumatica_create_ar_invoice and acumatica_release_ap_bill without opening any 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 a concrete precondition (only a Balanced invoice can be released) and a remediation path (set remove_hold to true for an On Hold invoice). It stops short of naming sibling alternatives explicitly, but the conditions for correct use are clear.

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