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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description's only added context is the set of fields returned, which is useful given there is no output schema, but it says nothing about pagination behavior or result ordering.

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?

A single front-loaded phrase with zero waste, but it is a fragment rather than a sentence and is arguably under-specified rather than genuinely concise. Nothing is padded, though.

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 four-parameter cursor-paginated list tool with no output schema, the description should at least signal that results are paginated via limit/cursor and that the field list is the row shape. It is adequate to identify the tool but leaves pagination behavior for the agent to discover.

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 75% and the three documented parameters (cursor, search, project_id) already explain themselves, so the baseline of 3 applies. The description adds a bit by naming 'project' and 'supplier' as the salient dimensions of a purchase order, which reinforces what project_id filters on.

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 is a noun phrase naming the resource (purchase orders) and the fields returned, so the agent can infer a list operation, but it never states a verb and never distinguishes itself from get_purchase_order (single record) or list_invoices/list_bills. The sibling name does most of the disambiguating work.

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?

There is no guidance on when to call this versus get_purchase_order or the other list_* tools, and no mention of prerequisites, scoping expectations, or how to page through results. Usage is only implied by the tool name.

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