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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no read-only confirmation, no mention of what a 'highlight' contains, no pagination or volume expectations. The only behavioral claim is the brand_hash prerequisite, which is already in structured data.

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 short sentences, front-loaded and free of padding, which is good. However, the second sentence duplicates the schema's required-parameter declaration rather than earning its place with new information.

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?

An output schema exists so return values need not be described, but for a tool with two opaque hash parameters and zero annotations, the definition should explain what a highlight is and how this result differs from get_audience or get_audience_patterns. That context is entirely absent.

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% and there are two required hash parameters. The description names only brand_hash (redundantly with the required list) and says nothing about audience_hash, nor about the format or relationship between the two hashes. It fails to compensate for the coverage gap.

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 restates the tool name ('audience highlights') with a modifier ('brand-specific') and never supplies a verb or scope. It gives no way to tell it apart from get_audience or get_audience_patterns, which are its closest siblings. This is effectively a tautology with a hint of extra meaning.

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?

'Requires brand_hash' states a prerequisite that the schema's required array already enforces, not a usage condition. There is no indication of when to choose this tool over get_audience, get_audience_patterns, or list_brand_audiences. No when-to-use or when-not-to-use guidance is present.

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