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

readOnlyHint=true already declares the safety profile. The description adds that results are paged and that next_offset is passed as offset, plus the underlying GET /item endpoint, but the pagination detail largely duplicates the offset parameter's own schema text, so the added behavioral context is modest.

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?

Three tight sentences: resource definition, valid filter fields, then pagination and endpoint. It is front-loaded and largely waste-free, though the filter-field list is dense enough to be borderline.

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 read-only list tool with 100% schema coverage and no output schema, it covers what an agent needs to call it: scope, valid filter fields, and pagination mechanics. Missing only routing guidance relative to get_item and the other list siblings.

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 baseline is 3, but the description adds real value: the filters.field schema explicitly defers valid field names to this description, and it enumerates them (item_id, name, external_key, accounting_sku, item_type, custom_1..3), including that item_type is service or discount. That is meaningfully beyond the schema.

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 (List) and resource (items) and immediately defines the resource as 'the products, services and discounts that go on invoices, quotes and subscriptions, with their pricing tiers.' That domain definition, plus the contrast with the singular get_item sibling, lets an agent identify the tool without opening a schema.

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 items' and the enumerated filterable fields, which tells the agent this is the browsing/search entry point. However, it never states when to use this versus get_item for a single record, or versus other list tools, and gives no exclusions.

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