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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds substantial behavioral detail: it fetches the homepage, takes the first <link rel='icon'> or 'shortcut icon' href, resolves to absolute URL, may return a data: URI, falls back to default favicon.ico without checking existence, and returns a source field with declared/default values. 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?

The description is two sentences, with the primary behavior front-loaded, followed by the fallback behavior and a usage note. Every sentence adds value, and there is no redundancy or fluff.

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?

The tool has a single parameter and no output schema, so the description carries the full burden of explaining the return behavior. It covers edge cases (no icon, homepage not fetchable), the source field, and the note, making it complete for an agent to call 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?

The schema already provides 100% coverage with a clear description of the 'domain' parameter. The description does not add new parameter-level meaning beyond confirming that the domain is the site to fetch from. Baseline 3 is appropriate because the schema carries the semantic load.

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 states the tool's purpose: it returns the favicon URL a website declares. It specifies the resource (favicon URL), the verb (returns), and explains the fetching logic and fallback. This distinguishes it from the many lookup/check tools in the sibling list, which are all security or data lookups.

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 gives a clear use case ('Use it to display a site icon') and explicitly states what it does not do ('does not download or validate the image'), which implies when not to use it. However, it does not name any specific alternative tool or exclusion condition, so it falls short of a 5.

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