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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this overwrites state. The description adds the source of the aggregation (run data) but does not disclose the destructive scope — that existing insights are replaced — or any cost/latency implications of regeneration. It adds context but not the behavioral detail that matters most for a destructive tool.

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 with no filler: the action and data source come first, the trigger condition second. The parenthetical enumeration is informative rather than redundant, though the sentence could be marginally tighter.

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 no output schema, the description must imply the return but instead focuses on the operation and trigger, which is reasonable for a regeneration call. For a destructive, 4-parameter mutation it leaves the overwrite semantics and inter-sibling routing implicit, but covers the essential trigger and data source.

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 (including the superadmin-only customerId, the timeFilter enum, and forceRegeneration) are already documented in the schema. The description only implies that inputs scope run data and adds no syntax or defaulting nuance beyond the schema, 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?

States a specific verb (Regenerate) plus the resource (aggregated agent insights derived from run data) and enumerates the insight contents. It does not distinguish itself from close siblings such as regenerate_run_insights, refresh_agent_analysis, or batch_regenerate_insights, so the agent must infer scope differences.

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?

"Use this after runs have been added or run insights regenerated" gives a concrete triggering condition. It stops short of naming alternatives or when-not-to-use conditions (e.g. when batch_regenerate_insights or refresh_agent_analysis is the better call), so routing among siblings is left to inference.

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