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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates stored state; the description's 'Regenerate' adds that it rebuilds aggregated insights from run data. It does not say whether existing insights are overwritten, whether the call is synchronous, or what happens if regeneration is unnecessary. Some added context, but thin against a destructive, non-read-only operation.

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 tight sentences: the action is front-loaded, the parenthetical enumerates outputs efficiently, and the usage trigger comes second. Nothing redundant or padded.

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?

For a destructive mutation with no output schema, the description leaves key gaps: whether it returns the regenerated insights or merely triggers a job, whether it is async/pollable, and any cost or rate implications. The schema fully covers inputs, but the behavioral envelope for a destructive tool is only partially described.

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 all four parameters (agentId, customerId, timeFilter, forceRegeneration) are already documented in the schema. The description adds no parameter detail beyond that, so the baseline 3 applies; the parenthetical describes output content, not inputs.

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?

Uses a specific verb (Regenerate) plus resource (aggregated agent insights) and states the source data (run data) with a parenthetical of what the insights contain. This clearly separates it from run-level peers like regenerate_run_insights, but it never names or contrasts a sibling explicitly.

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?

Gives an explicit trigger: 'Use this after runs have been added or run insights regenerated,' which tells the agent the precondition. It stops short of exclusions or alternatives (e.g., batch_regenerate_insights, refresh_agent_analysis), so selection between peers still requires inference.

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