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

Annotations already cover the read/write and open-world profile, and the description adds meaningful extras: hold semantics and downstream releasability, that taxes follow the Acumatica setup, that confirmation happens per call by default, and that a Cotlet API key with app access is required. It does not describe rate limits or failure behavior, keeping it out of 5 territory.

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 purpose and the key hold behavior, and the operational notes (confirmation, API key) are grouped at the end. 'On Hold by default' and the subsequent 'with hold set to true, the default' are redundant, costing a little efficiency.

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?

With no output schema, the description still conveys what the call produces (an invoice in Invoices and Memos, held or balanced), the confirmation requirement, and the auth prerequisite. It omits what the response returns (e.g., invoice ID), which an agent might want for a follow-up release call.

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%, so all four parameters are already documented, including hold's default and customer_id's source (list_customers). The description adds the line-total formula but otherwise restates schema content, matching the baseline 3.

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 and resource ('Create an AR invoice for a customer with one or more lines') and scopes the record placement to 'Invoices and Memos'. This clearly separates it from the sibling release_ar_invoice and from acumatica_create_ap_bill.

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 clear context: creates as On Hold by default, use hold=false to get a Balanced invoice that can then be released, implying release_ar_invoice is the follow-up step. No explicit 'when not to use' or named sibling routing, so it falls short of a 5.

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