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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds no behavioral context: it says nothing about caching, extraction depth, external fetch behavior, or what happens when the domain is unreachable, even though the parameters hint at such traits.

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?

A single front-loaded sentence with zero filler. It is efficient, though arguably undersized for a five-parameter profiling tool whose behavior is not self-evident.

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 a full schema and an output schema present, the description needn't explain returns, and annotations cover safety. Still, for a brand-profiling tool with five parameters, the description is thin enough that an agent lacks context on what the profile is or how the domain is interpreted.

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 the schema already documents all five parameters thoroughly, including clamping ranges, defaults, and the no-op ForceLanguage. The description adds no additional parameter meaning, making the baseline 3 appropriate.

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 (retrieval) and resource (brand profile) scoped to a domain, so an agent can tell it fetches a brand profile rather than searching. However, it does not define what a 'brand profile' contains or distinguish itself from the many other brand-related sibling tools, leaving differentiation to inference.

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 offers no when-to-use guidance, no prerequisites, and no alternatives. It is implied that one calls it to get a brand profile for a domain, but nothing tells the agent when this is preferable to a site-specific brand tool or a search tool.

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