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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=falsetalkative, so the description's job is lighter. It does add one behavioral detail—paginated results—but says nothing about match semantics (exact vs fuzzy), rate limits, or error cases. No contradiction with annotations.

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?

One short sentence front-loads the main purpose (search scans by favicon hash) and tags the pagination behavior. No filler or repetition.

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 low-complexity search endpoint with a rich output schema and safe-read annotations, the one-line description is largely sufficient to invoke it. The remaining gap is differentiation from the sibling search_favicon_mmh3, but that is not essential to making a correct call.

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 0%, and the description only says 'favicon hash,' implicitly mapping to hash_value. It does not explain the relationship between hash_value and hash_type, the meaning of mmh3 vs md5/normalized hash variants, or what pagination parameters control beyond their defaults in 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 uses a specific verb ('Search') and a clear resource ('scans') with a distinct search key ('favicon hash'), so an agent can tell what the tool does. It does not explicitly distinguish itself from the sibling search_favicon_mmh3, though the hash_type parameter implies broader hash support (both mmh3 and possibly others).

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?

No usage guidance is provided: the description does not explain when to choose this tool over search_favicon_mmh3 or search_by_screenshot_hash, nor does it note whether hash_type affects use cases. The agent must infer context from the tool name and schema.

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