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

Annotations already establish this as a safe, read-only, idempotent lookup. The description adds meaningful result semantics beyond them: each result is marked direct (with footprint) or adapter (with plate chain), and it warns not to conflate adapter fits with direct fits or 'unknown' with 'does not fit'.

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?

The description is front-loaded with the core action and result semantics, then gives precise reporting rules. It is dense but every sentence contributes; minor tightening could improve it without changing meaning.

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?

There is no output schema, so the description carries the burden of explaining return semantics. It covers the direct/adapter distinction, footprint and plate chain fields, unknown handling, and citation/link requirements, which is sufficient for an agent to use the results correctly.

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?

With one required parameter and 100% schema description coverage, the schema already explains that the optic may be a slug or name. The description reinforces the single-optic scope but adds no format or validation detail beyond the schema.

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 states a specific verb and resource ('List every pistol') scoped to one optic, and its fit-marking behavior distinguishes it from siblings like list_optics_for_pistol and check_fit. An agent can tell exactly what this tool retrieves 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?

It gives a clear use case ('what pistols take this red dot') that maps directly to the tool's scope. It does not explicitly name alternatives such as check_fit or list_optics_for_pistol or state when not to use this tool, so guidance is strong but incomplete.

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