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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the underlying endpoint, GET /PurchaseOrders/{page}, which reinforces the read-only and paginated nature, but it does not disclose rate limits, authentication requirements, or pagination behavior beyond the schema's page parameter.

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?

Two tightly written sentences with no filler. The core operation is front-loaded, followed by filter scope and the API endpoint, all of which earn their place.

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 list tool with no output schema, the description is reasonably complete: it covers the operation, filter scope, and endpoint. The main omission is that return shape and pagination totals are not described, but the schema covers pagination inputs and the annotations cover safety.

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 all 12 parameters are already documented in the schema. The description names several filter categories but does not add syntax, defaults, or filtering behavior beyond what the schema provides, making the baseline 3 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 states a specific verb and resource: 'List purchase orders.' It also names the filter dimensions, so the agent can immediately distinguish this from sibling list tools for sales orders, products, and customers.

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 purchase orders, filtered by...' but the description does not state when to use this versus unleashed_get_purchase_order for a single order, nor does it mention prerequisites such as authentication or required permissions. It gives adequate context for a list operation but stops short of explicit alternative guidance.

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