brand_retrieve

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

No annotations provided, so the description carries full burden. It describes the fetch and extraction process, including that enrichment-only fields return null, but lacks details on performance, caching, failure modes, or any side effects. This is adequate but not comprehensive.

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 concise, front-loading the purpose and then detailing what is extracted. It is efficient with no wasted words, though it could be slightly more structured (e.g., bullet points).

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 no output schema, the description partially explains the output (normalized brand profile with fields like title, colors, logos, etc.). However, it lacks details on error handling, caching behavior, or the exact structure of the response, making it moderately 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?

Schema description coverage is 100%, so each parameter is documented in the schema. The description adds context about the output (e.g., enrichment fields returning null) but does not significantly enhance understanding of the parameters beyond the schema's descriptions.

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 verb 'Retrieve', the resource 'brand data by domain', and the action of fetching homepage and Web App Manifest to extract a normalized brand profile. It distinguishes itself from sibling tools which are focused on specific platforms (e.g., Amazon, Airbnb) by being a general web brand retrieval tool.

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 implies usage for retrieving brand data from a domain but does not explicitly state when to use this tool versus alternatives. There is no exclusionary guidance or mention of when not to use it, leaving the agent to infer from sibling tool names.

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