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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds real context beyond them: result cap of 10, best-match ordering, and the ILIKE+trigram matching semantics. It also discloses the exact return shape, which matters since 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?

Three tight sentences, front-loaded with what the tool is and what it returns. The alternative-usage note is placed last where it belongs. No wasted text.

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 compensates fully by enumerating the return fields `{itemdefid, name, icon_url}` and the ordering guarantee. For a one-parameter read tool, nothing an agent needs to invoke or interpret the result is missing.

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% and the single `q` param is fully documented in the schema (min 2, max 100 chars). The description adds meaning beyond that by clarifying that `q` matches against skin *names* via substring/trigram matching and that results are ranked by match quality.

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+resource (skin name typeahead) plus concrete scope: up to 10 skins, matched on `q`, best match first. An agent can distinguish this from browse_skins or search_items immediately.

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?

Explicitly says to use the returned `itemdefid` with the other skin endpoints, and routes filtered/paginated needs to GET /skins with `search=`. The only friction is that the alternative is named as a raw REST endpoint rather than the sibling tool name (browse_skins), requiring a small inference.

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