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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: it discloses the shape of the result (slugs, names, page URLs) and its role as a feeder for other tools — important 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 short sentences, front-loaded with the resource list, then output shape, then the usage condition. No filler.

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 only two params and no output schema, the description compensates by describing return fields and the downstream workflow. Minor gaps remain — no mention of result limits, ordering, or behavior when nothing matches — but nothing critical for correct invocation 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 both parameters are documented with an example, so the schema carries the semantics. The description only loosely reinforces that matching is by name; it adds no detail on the `type` filter or match behavior, so 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 (find) and the exact resources covered (pistols, optics, footprints) plus the lookup key (name). This clearly separates it from siblings like get_footprint or check_fit, which take exact identifiers rather than fuzzy names.

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 it when you are unsure of an exact model name" gives a clear triggering condition, and "pass to the other tools" frames it as the discovery step in a workflow. It stops short of naming which sibling to use once an exact name is known, so it isn't fully explicit about alternatives.

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