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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: the auth prerequisite ('Needs the user's Cotlet API key with access to this app') and the note that search matches the name as Acumatica displays it.

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 what the tool returns, then filters, then downstream usage and auth. Four short sentences with mild redundancy between 'Vendors ... with their ID, name and status' and 'Lists vendors, filtered by ...', but no filler.

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?

A read-only list tool with no output schema, so describing the returned fields (ID, name, status) is genuinely useful, and the auth requirement plus downstream vendor_id use round it out. Only missing detail is pagination behavior, which the cursor parameter already implies.

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 schema already documents limit, cursor, search and status; baseline is 3. The description adds only a marginal clarification to search ('matches the vendor name as Acumatica shows it') and restates the filterable dimensions, adding little beyond 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 and resource ('Lists vendors') and enumerates the returned fields (ID, name, status), plus the two filter dimensions. It even names sibling tools (create_ap_bill, list_bills) that consume the vendor_id, so an agent can place it precisely in the workflow.

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 for use by telling the agent to take vendor_id from each item into create_ap_bill and list_bills, i.e. it's the lookup step. It gives no explicit when-not guidance and no alternatives, but no competing vendor-listing sibling exists for Acumatica.

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