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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real value on top: the world-reset-only scope exclusion and the sort contract ('by level, or by one bonus, highest first'), which affects how results should be interpreted. It stays silent on the default/variable result count and result ordering stability beyond the sort key.

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?

Front-loads the data categories in the first clause, then adds scope and sorting constraints in two short sentences. Slightly dense prose with a long parenthetical subtype list, but no filler sentences.

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 13-parameter read-only search with no output schema, the description covers the data domain, scope limits and sorting, which is enough to call it correctly; remaining details (level bounds, limit, include_limited, magic_type) are handled by the schema's enums and descriptions.

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 high (69%) with enums on the key filters, and the description still contributes meaning beyond it: it clarifies that sorting can be by level or by a single bonus (highest first), distinguishing damage from stat bonuses. That matches the schema's sort semantics without contradicting them; with coverage this high the schema carries the enumerated values.

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 enumerates the exact resource set (armor/gear, weapons, magic items listed by subtype, pets) and states what each result carries — stats, who may use it, source zone and mob. That is a specific verb-implied resource definition an agent can match to a user request without opening the 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?

One genuine usage constraint is given: 'Only items placed in the world by zone resets are listed', which tells the agent this won't answer questions about shop or quest-only items. There is no explicit when-to-use framing and no named alternative (siblings — help_*, news_*, who — are unrelated domains, so the cost is low).

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