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

The readOnlyHint annotation already declares this a safe read, lowering the bar. The description adds the underlying endpoint (GET /PurchaseOrders/{page}), confirming a paginated read, but says nothing about defaults, rate limits, or result shape beyond what the schema shows.

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 sentence plus a compact endpoint reference, front-loading the action and its filters with no filler. The endpoint notation is slightly terse but earns its place by grounding the tool in the actual API.

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 12-parameter, 0-required read-only list tool with no output schema and a readOnlyHint, the description adequately conveys scope and filterability. The only mild gap is the absence of any note on pagination behavior or expected volume, which the schema partially covers.

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 100%, so the schema already documents all 12 parameters including formats, ranges, and status values. The description restates the filterable fields at a high level without adding syntax or semantics beyond the schema, which is the expected baseline.

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 states a specific verb and resource ('List purchase orders') and enumerates the filter dimensions, which is clear. It does not explicitly differentiate itself from the sibling unleashed_get_purchase_order, though 'list' vs 'get' is largely self-evident.

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?

Usage is implied by 'list ... filtered by', so an agent can infer this is the bulk/browse retrieval path. However, there is no explicit when-to-use guidance, no mention of when to prefer unleashed_get_purchase_order for a single record, and no stated prerequisites.

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