list_purchase_documents

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

Description only mentions default sort order. No annotations provided, so the description carries full burden. Lacks details on read-only nature, pagination, filtering, or other behaviors. Schema covers parameters but not behavioral traits.

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?

Single sentence front-loads core purpose and default sorting. No wasted words; highly efficient.

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?

Despite having an output schema and full parameter descriptions, the tool has 7 parameters and no annotations. The description is too minimal to provide complete context for an AI agent, lacking explanation of what constitutes a purchase document or when to use filters.

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% with descriptions for all 7 parameters. Description adds no extra meaning beyond what schema already provides. Baseline of 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?

Description uses specific verb 'list' and resource 'commercial purchase documents', clearly differentiating from sibling tools like get_purchase_document (single) and list_sales_documents (sales).

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?

Implied usage: use to list purchase documents. No explicit guidance on when not to use or alternatives among siblings, but the purpose is straightforward.

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