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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds non-obvious operational facts: default page size of 25, a hard cap of 200 rows, and the POST /purchases/orders/list transport. It does not describe error behavior or ordering guarantees, but adds meaningful context beyond the annotations.

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?

Four short sentences, front-loaded with purpose then capabilities then paging mechanics then field syntax. Dense but everything earns its place; the row-limit fact is stated twice (prose and schema), a minor redundancy.

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 5-parameter, all-optional list tool with no output schema, it covers selection, projection, sorting, paging and the entity field vocabulary. It stops short of describing the response envelope (total counts, result wrapper), which matters without an output schema, but an agent has enough to invoke it correctly.

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%, so the baseline is 3; the description goes further by naming the Laudus field-naming convention and concrete dotted paths (purchaseOrderId, supplier.name, items.product.sku, items.quantity) that an agent would not know from the generic schema strings alone. The only overlap is the repeated limit/paging rule.

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?

States a specific verb and resource ('List purchase orders') plus the supported capabilities (filters, sorting, field selection, paging) and the Spanish alias 'ordenes de compra'. The plural 'List' implicitly distinguishes it from laudus_get_purchase_order, though no sibling is named explicitly.

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?

It gives an actionable pagination rule ('When a page is full, ask for the next one with offset = offset + limit'), which is real usage guidance. However, it never states when to use this versus laudus_get_purchase_order or the adjacent list tools (sales orders, purchase invoices), leaving retrieval-vs-search selection to inference.

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