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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds little beyond that — 'Returns progress summary' hints at the output shape, but nothing about the overwrite behavior of `force` or the batch limit, which lives entirely in the schema.

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?

Three short sentences, zero filler, with the core action front-loaded and the usage trigger immediately after. Every sentence carries 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?

For a destructive batch mutation with no output schema, the description is thin: it does not mention the default limit of 50 (which bounds scope), the overwrite behavior, or how it relates to the single-run sibling. The 'progress summary' note partially covers the return, but an agent must open the schema to understand the operation's blast radius.

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 coverage is 100%, and the schema descriptions are rich (overwrite semantics, defaults, max values, superadmin restriction). The description contributes no parameter detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 resource (insights) with a clear scope qualifier ('for all runs of an agent'), which distinguishes it from a single-run variant. However, it never contrasts itself with close siblings like regenerate_run_insights or refresh_agent_insights, so the boundary is inferred rather than stated.

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 to bulk-fix broken insights or refresh after changes' gives concrete when-to-use triggers. It stops short of naming alternatives (regenerate_run_insights, refresh_agent_insights) or when-not conditions, so an agent could still pick the wrong sibling for a single run.

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