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

Beyond annotations, the description discloses that the tool 'regenerates EVERY target itself in a single call (1 credit per agent)', returns 'the real new signed avatar_url for each', and instructs reporting only agents in the `regenerated` array. It also explains sensitive-tier approval semantics. No contradiction with destructiveHint=true.

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 organized into purpose, routing, and approval blocks, with each sentence earning its place by covering target selection, batching, cost, result handling, or approval behavior. It is longer than minimal, but the structure keeps it digestible and front-loaded with the primary use case.

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 7 parameters and no output schema, the description still explains target selection, batch behavior, per-agent credit cost, the `regenerated` result contract, and approval flow. The schema covers remaining parameter details, making this adequately complete for correct invocation and result interpretation.

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%, and the schema already documents each parameter including precedence of `all` and the meanings of `agent_ids`, `agent_names`, `style`, and `companyId`. The description restates the pass modes but adds no new parameter-level semantics beyond what the schema provides, so baseline 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?

The description states a specific verb ('Generate or regenerate') and resource ('AI agent profile avatar(s)'), scoped to 'a company's AI team'. It distinguishes this tool from generic agent update tools by focusing exclusively on avatar generation/regeneration and by enumerating the supported invocation modes.

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?

It explicitly says 'Use when an operator wants to create, refresh, or restyle one or more agents' profile avatars' and gives strong routing guidance, including 'never call once per agent or enumerate the roster yourself; use agent_ids[]/agent_names[]/all:true for multiple.' It does not name a sibling alternative tool to select instead, but the when-to-use and batching rules are clear.

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