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

Adds substantial behavior beyond the annotations: the bill lands On Hold by default and cannot be released until the hold is removed, taxes/approvals can push it to Pending Approval, the total is the sum of lines, confirmation is required by default, and a Cotlet API key with app access is needed. That covers side effects, downstream workflow state, and auth, though the safety profile itself is already carried by readOnlyHint=false and destructiveHint=false.

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?

Purpose is front-loaded, but the confirmation requirement is stated twice ('By default you confirm each call...' then 'confirm with the user before each call') and the hold default is restated after being introduced in the first sentence. The redundancy costs efficiency without adding 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 write tool with no output schema, the description covers the important unknowns: it is a creation in a specific Acumatica area, it defaults to On Hold, approvals may intervene, and confirmation/auth are required. It stops short of describing what the response returns, but that gap is minor for this tool class.

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 the schema already documents all six parameters including the hold default and line structure. The description adds only marginal meaning (total = sum of lines) beyond what the schema provides, so the baseline 3 is correct.

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 AP bill for a vendor with one or more lines') and scopes it to one vendor in 'Bills and Adjustments'. The AP/vendor framing implicitly distinguishes it from the sibling create_ar_invoice, so an agent can route correctly 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?

Explains the default hold state, the approval outcome, and the per-call confirmation requirement, which is useful operating context. However, it never names when to prefer this over alternatives or when-not to use it (e.g., versus approve_bill_for_payment or release_ap_bill), so usage is only implied.

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