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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the result format ('prefix:name'), the style variants returned, the official hex color, and the fact that SVG retrieval requires a follow-up call.

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?

Front-loaded with the core action and input, then return shape and next step. The final sentence about client rendering (color swatch and clickable grid) is the least essential, but the overall length is reasonable for the amount of return information conveyed.

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?

With no output schema, the description carries the return-value burden and does so well: match format, style metadata, and hex color. It omits result-count limits and no-match behavior, which keeps it short of fully complete for an open-ended lookup.

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 100% with a single parameter, so the schema already documents 'brand' fully. The description's examples ('Stripe', 'vercel.com') mirror what the schema already gives, adding no new syntax or format constraints — baseline 3 applies.

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), resource (brand logo), and accepted inputs (company/product/technology name or domain), which cleanly separates it from generic icon tools. It does not, however, name any sibling tool, so an agent must infer the boundary with search_icons and get_icon.

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?

Usage is implied by the input shape — use this when you have a brand name or domain rather than a visual description. There is no explicit when-not guidance and no alternative (search_icons, get_icon) is named, so routing is left to inference.

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