get_purchase_orders

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

With no annotations, the description carries the burden of behavioral disclosure. It only repeats the tool's name and does not disclose pagination, default ordering, result structure, or any side effects. The sparse description adds no value beyond what the name already implies.

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 a single, front-loaded sentence that communicates the core purpose efficiently. No excessive words or redundant details, making it appropriately sized for a simple list operation.

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?

For a straightforward list tool with fully documented parameters, the description is adequate. It lacks return-value details, but this is acceptable given no output schema and the tool's simple nature. While annotations are absent, the read-only nature is implied by 'List', making the tool usable.

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?

The input schema describes all three parameters (limit, offset, search) with clear descriptions, covering 100%. The tool description adds no parameter details, so it does not enhance schema semantics. Baseline 3 is appropriate since schema already handles explanation.

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 purchase orders, using a specific verb ('List') and resource ('purchase orders'). It distinguishes from sibling tools like get_orders by narrowing to purchase orders, and the Russian translation adds clarity about the domain.

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?

No guidance is provided on when to use this tool vs alternatives like get_orders or get_customer_order. The description implies usage but does not state exclusions or prerequisites, leaving the agent to infer context.

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