list_sales_documents

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

Without annotations, the description must convey behavioral traits. It discloses pagination and field selection behavior, implying a read-only list operation. However, it does not explicitly state that the tool has no side effects, rate limits, or authentication requirements, leaving some ambiguity.

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?

The description is two sentences, front-loaded with the primary purpose, and zero waste. Every sentence adds value: the first defines the action and default sort, the second instructs on pagination and field filtering.

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?

Given 7 parameters, 100% schema coverage, and an output schema, the description is adequate but not exhaustive. It covers the main usage pattern (pagination and field selection) but omits mentioning key filters like document_type or customer_id, which are documented in 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 baseline is 3. The description adds no additional meaning beyond what the schema already provides (e.g., pagination hints are already in parameter descriptions). It does not compensate for any schema gaps.

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 clearly states the tool lists commercial sales documents with default newest-first ordering. It uses specific verb 'list' and resource 'sales documents', distinguishing it from sibling list tools for other entities like customers, products, or purchase documents.

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?

The description lacks explicit guidance on when to use this tool versus alternatives like list_sales_receipts or get_sales_document. It does not mention prerequisites or exclusion scenarios, leaving the agent to infer usage context from the function name alone.

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