get_purchase_orders

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

With no annotations provided, the description carries the full burden. It only says 'List all purchase orders' without disclosing that this is a read-only operation, that results are paginated, or any potential side effects or requirements. The pagination parameters hint at behavior, but the description does not explicitly explain the retrieval semantics.

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 concise and front-loaded with the main purpose. The Args list is minimal but earns its place since the schema lacks descriptions. No wasted words, though the structure is a bit mechanical.

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 simple list tool with only two integer parameters and an output schema, the description is adequate on the surface. However, it leaves ambiguity around whether 'all' means the entire dataset or a single page, and it does not clarify pagination behavior or ordering. It lacks enough context to be considered fully complete.

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 0%, so the description must compensate. It provides only terse one-line explanations ('Page number', 'Results per page') that do not go beyond what parameter names already imply. It fails to mention defaults, ranges, or how pagination interacts with 'all'.

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 'List all purchase orders' – a specific verb ('list') and resource ('purchase orders'). The name itself is unambiguous, and no sibling tool targets purchase orders, so it distinguishes from alternatives.

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 implies usage by stating the core action, but it does not explicitly mention when to use this tool versus alternatives or when not to use it. Since no alternative purchase-order list tool exists among siblings, the guidance is solely implicit.

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