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

Annotations already establish readOnly=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds useful non-schema context (the Cotlet API key must have access to this app), but says nothing about pagination behavior or result volume despite a cursor/limit schema being present.

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?

Four sentences, front-loaded with what is listed and filtered, and each sentence carries distinct information (scope, filters, use case, auth). The opening fragment 'AP bills with vendor, vendor reference, dates, amount and status' is slightly list-like but still informative.

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 compensates by naming the returned fields, the source object, the filterable dimensions, and the auth requirement. Only the pagination contract (limit/cursor semantics) is left implicit for the caller to infer from the schema.

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 limit, cursor, status, vendor_id and vendor_ref, including the enum values the description redundantly restates. The only added meaning is the dedup rationale for vendor_ref, which is really usage guidance rather than parameter semantics.

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 gives a specific verb and resource ('Lists AP bills from Bills and Adjustments') and enumerates the fields and supported filters, so the agent knows exactly what comes back. It stops short of distinguishing itself from the close sibling acumatica_list_bills_for_payment_approval, which also surfaces bills in approval-related states.

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?

It supplies a concrete when-to-use rule: call it with the vendor_ref filter before creating a bill to avoid duplicating a vendor invoice. That is genuinely actionable, but no alternatives are named and no when-not-to-use condition is given vs. list_bills_for_payment_approval.

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