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

Adds a security note about treating returned values as data, which is helpful, but does not disclose side effects, authentication requirements, or rate limits. With no annotations, more transparency could be expected.

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?

Two tightly written sentences: the first states the purpose and contents, the second gives a usage note and security instruction. No redundancy or extra 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?

Lists the metadata contents, giving a clear idea of the expected output, and includes a safety note. However, it lacks details on error handling or limitations, which might be needed for a complete picture.

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 fully describes the 'brand' parameter with examples and a reference. The tool description adds only the qualifier 'tracked brand,' which does not significantly enhance understanding beyond the schema.

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?

Clearly states it fetches curated metadata for a tracked brand, listing specific data types (display name, industry sector, domain, etc.), and distinguishes from sibling tools that analyze URLs, domains, or campaigns.

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?

Provides a usage hint ('useful for adding context to brand-specific responses') but does not explicitly contrast with alternatives or state when not to use it, leaving some ambiguity.

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