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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds genuinely new context: the exclusion rule for seasonal/obsolete/unreleased items, the routing to shortname resolution, and a stated 15-minute cache aligned with the site's /items page. That cache and staleness disclosure is exactly the kind of behavioural trait annotations cannot express.

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 sentences, each carrying a distinct load: what it does and its scope, what each result contains plus where to go for more, and the ordering/cache contract. Scope and exclusions are front-loaded; nothing is redundant against the schema or annotations.

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, the description correctly enumerates the returned fields (shortname, display_name, category, icon_url, is_craftable) and explains that richer data requires the detail endpoint. Combined with the cache TTL and exclusion rules, an agent can call this correctly; only pagination totals/result-count behaviour is unstated.

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 all five parameters (page, sort, search, category, per_page) are already fully documented including fuzzy-match semantics and ranking behaviour. The description adds no parameter-level meaning beyond what the schema provides, 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?

The description opens with a specific verb+resource ('Browse or search the item catalogue') and immediately narrows the scope to 'one page of live items', which is a meaningful distinction. It signals a sibling boundary by pointing to `/items/{shortname}` for full details, though it never names get_item or search_items explicitly.

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 rather than stated: it explains that seasonal/obsolete/unreleased items are excluded from browsing but still resolve by shortname, and that the detail endpoint should be used for 'everything else'. There is no explicit statement of when to call browse_items versus search_items or get_item, so the agent must infer the routing.

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