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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds value beyond annotations by disclosing the return shape (a HAL collection embedding fx:items), which matters because there is no output schema, and by exposing the backing endpoint GET /transactions/{transaction_id}/items.

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 short sentences, front-loaded with the purpose before the technical return/endpoint detail. Every clause earns its place with no filler or restated title.

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 simple read-only list tool, the description covers purpose, return format, and the upstream endpoint, while the annotations cover the safety profile and the schema covers all four parameters. The absence of an output schema is compensated by the stated HAL collection return shape.

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 zoom, limit, offset and transaction_id are already documented in the schema. The description adds no parameter-level detail (e.g. what zoom values expand, pagination semantics), so the baseline 3 applies.

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 the line items of a transaction') and clarifies with '(the products purchased)', so an agent distinguishes it from foxy_get_transaction and foxy_list_transactions without opening the schema. The underlying hAPI route is named, reinforcing exactly what is retrieved.

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: you call this when you already have a transaction and need its purchased products, as opposed to foxy_get_transaction for the transaction itself. However, no explicit when-to-use or when-not-to-use guidance is given, and no alternative is named.

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