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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safe-read behavior is covered. The description adds useful output details (size, hashes, base64 image) but does not disclose any further behavioral traits such as potential missing favicons, error conditions, or format quirks. With annotations carrying the safety profile, this is adequate but not exceptional.

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 two short sentences, front-loads the core purpose and output contents, and adds the pivot instruction without wasted words. Every sentence 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?

Given the tool's simple one-parameter schema, strong annotations, and the presence of an output schema, the description covers the essential purpose, output shape, and a common follow-up action. It could additionally mention what happens when no favicon exists, but for this simple read tool it is largely complete.

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?

The schema has only one parameter, scan_id, and the description clarifies it is the scan identifier for which the favicon is fetched. With 0% schema description coverage, the description provides the necessary basic context but does not explain where scan_id comes from or any format expectations. For a single simple parameter this is minimally viable.

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 clearly identifies the tool's function: retrieving a favicon for a scan_id and enumerates the exact output contents (size, hashes, base64-encoded image). This distinguishes it from related sibling tools like get_favicon_stats and search_by_favicon by defining what this specific endpoint returns.

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 actionable downstream guidance: 'Use the md5 with search_by_favicon to pivot.' This explicitly connects the tool to a sibling workflow. It does not, however, contrast this tool with get_favicon_stats or explain when not to use it, so it stops short of full when-to-use vs. alternative coverage.

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