list_purchase_orders

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds no further behavioral context, such as pagination behavior, default ordering, or that it returns a list in chunks, and therefore adds no value beyond the annotations and schema.

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, short sentence that is easy to parse and front-loaded. It is appropriately concise for a simple list operation, though it could include a bit more substance without losing efficiency.

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?

With no output schema and a minimal description, the tool is only minimally complete. The schema covers parameters and annotations cover safety, but the description does not state what the response contains or that it supports pagination, which would be helpful for a list endpoint.

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 provides 100% coverage for limit, offset, and order_by with clear descriptions, including the max limit of 2000 and sort syntax. The tool description itself adds no additional parameter meaning, so a baseline score 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?

The description uses the verb 'Fetch' and identifies the resource 'purchase orders', which clearly aligns with the tool's name and distinguishes it from single-record operations like get_purchase_order. However, it lacks any scope qualifier (e.g., 'all', 'paginated') that would further clarify what kind of list is returned.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this is the sole listing tool for purchase orders, nor does it suggest using get_purchase_order for individual records.

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