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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that—no pagination behavior, no default result count, no note that returns are unfiltered—so it contributes no behavioral context.

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 single sentence is waste-free but only because it contains no substantive content; it is under-specification rather than conciseness. Nothing is front-loaded because nothing is provided.

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 three-parameter list tool with no output schema and no parameter documentation anywhere, the description should explain the filters and return shape. It supplies neither, leaving the agent unable to invoke the filters correctly, though the annotations at least cover safety expectations.

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% for all three parameters (search, status, supplier_id), and the description mentions none of them. The agent has no idea what values status accepts, what search matches on, or whether supplier_id is a UUID or name—the description does nothing to compensate.

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 restates the tool name and title verbatim ("List purchase orders"), adding no information about scope, filtering, or what distinguishes it from siblings like get_purchase_order or list_sales_orders. It is pure tautology rather than a description of purpose.

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 use this tool versus the many related siblings (get_purchase_order, list_sales_orders, list_suppliers, search_items). The agent must infer that this is the unfiltered browse variant with no stated prerequisites or alternatives.

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