Icon external

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

The annotations already declare openWorldHint=true and destructiveHint=false, and the description adds useful context that this operation may cache the favicon. This helps explain readOnlyHint=false, since caching can involve a write, but the description does not cover failure behavior, cache invalidation, rate limits, or return format.

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 definition is a single front-loaded sentence with no filler. It communicates the core operation compactly, though its brevity means other dimensions carry the missing detail.

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 favicon-fetch tool, the description plus annotations gives enough context to know it fetches an external favicon by hostname. However, with 4 parameters and 0% schema description coverage, no output schema, and no sibling guidance versus vaultwarden_icon_internal, it remains minimally complete rather than fully informative.

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% across 4 parameters, and the description only clarifies the required host parameter as a hostname. The form, params, and json_body parameters are neither documented in the schema nor explained in the description, leaving most parameter semantics uncovered.

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: fetch/cache a site favicon by hostname from the internet. It is clear what the tool does, but it does not name or distinguish itself from the sibling vaultwarden_icon_internal, so the sibling differentiation is left only to the parent tool name.

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 phrase 'from the internet' implies an external-source favicon fetch, but the description gives no explicit when-to-use guidance, no conditions, and no mention of the vaultwarden_icon_internal alternative. An agent must infer the usage boundary from the tool name alone.

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