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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context about the payload shape (each group's member brands and rollup stats), which the annotations do not express.

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-loads the action and resource, then spends two short sentences on the term definition and the return contents. Nothing is wasted, though the parenthetical gloss and the definition sentence overlap slightly.

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?

There is no output schema, but the description compensates by naming what is returned (member brands, count, last-updated, average visibility), and annotations carry the safety profile. For a parameterless read tool this is close to fully self-sufficient; only the absence of any usage routing keeps it below 5.

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?

One parameter (user_intent) with 100% schema description coverage, so the schema fully documents it. The description adds no syntax, format, or behavioral detail about that argument, so the baseline of 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 and resource ('List brand groups') and immediately disambiguates the resource with a plain-language gloss ('agency portfolios') plus a definition of what a brand group is. That distinction is what separates it from the sibling list_brands, so an agent can pick the right tool without opening either schema.

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 establishes the domain ('a collection of brands an agency manages on behalf of multiple clients') from which usage is implied, but it never says when to call this versus list_brands or any other listing tool. No prerequisites, no exclusions, no explicit alternative routing.

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