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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing the shape of the response (id, name, currency, unit cost, type, taxable) and the underlying GET /items endpoint, which matters because there is no output schema.

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 compact sentences, front-loaded with the resource and the returned fields, followed immediately by the actionable linkage to draft-invoice creation. Nothing is padded; even the endpoint hint is a single token.

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?

With no output schema, listing the returned fields is the right compensating move, and pagination/sorting/filtering are fully documented in the schema. Minor gap: it does not mention the paging envelope (next_page/total) or that results may span multiple pages, though the page param hints at it.

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% (page, sort, filter, per_page, updated_after are all documented, including next_page chaining and filter syntax), so the schema carries the burden. The description adds nothing about parameters beyond the `catalog_item` naming note, which is not a parameter of this tool; 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 item catalog (products and services)') and enumerates the fields returned, so the agent knows exactly what data comes back. It is naturally distinguishable from sibling list tools, but it never explicitly differentiates itself from invoiced_get_item or the other invoiced_list_* endpoints.

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?

'Use item ids as `catalog_item` when creating a draft invoice' links the result to a concrete downstream use (invoiced_create_draft_invoice), which implies why you would call this. However, it gives no guidance on when to prefer this over invoiced_get_item for a single item, and no exclusions or preconditions.

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