List Sale Invoices

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, so safety is covered. Description adds value by disclosing pagination, server-side filtering, and default brief view. No contradiction with annotations.

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?

Two efficient sentences with no fluff. Every sentence adds value: first states purpose and pagination/filters, second clarifies view and alternative tool.

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?

Lacks output schema details (e.g., pagination metadata, shape of invoice objects). But for a standard list tool, the description is sufficient to infer a paginated list. Slightly incomplete without mentioning response structure.

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 has 100% coverage with descriptions for all 8 parameters. Description does not add new parameter-level detail beyond summarizing filters; baseline 3 is appropriate.

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?

Clearly states 'List sales invoices' (specific verb+resource). Distinguishes from siblings like get_sale_invoice and other list_* tools by mentioning pagination and server-side filters. Implicitly separates from get_sale_invoice for detail.

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?

Provides guidance on when to use view='full' vs get_sale_invoice for detail. Implies that list_sale_invoices is for listing with filters, not for single invoice detail. However, does not explicitly mention when not to use or alternative sibling tools.

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