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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds scoping context ('usable' presets, 'exact' models), but does not describe filtering behavior, result limits, or pagination.

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?

A single front-loaded sentence enumerates scope and search fields with no filler. Every clause earns its place.

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 simple read-only search tool with annotations covering safety and no output schema, the description is nearly complete: it names the resource and all search dimensions. The only gap is that limit/pagination behavior is not mentioned, which is a minor omission.

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 description coverage is exactly 50%: the query field is well documented in the schema, and the description repeats essentially the same searchable fields without adding syntax or format details. The limit parameter is undocumented in both schema description and tool description, leaving its behavior (max 20, default 10) unexplained beyond the raw JSON constraints.

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 resource (drawer presets, Eurobox/KLT models) with the searchable fields enumerated. The distinction from sibling generate_* tools is clear from the verb, though no alternative is named 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?

The description explains what can be searched, but gives no guidance on when to use this tool instead of find_gridfinity_printers or the generate_* siblings. No prerequisites, exclusions, or alternative-selection context are provided.

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