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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation/overwrite profile is disclosed structurally. The description adds that a progress summary is returned and frames the bulk-fix/refresh use case, but the overwrite semantics ('existing insights overwritten on success') live only in the schema, not the description. Adequate additional context, not rich.

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, front-loaded with purpose and followed by usage and return behavior. Every sentence earns its place with no redundancy.

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 batch mutation tool with no output schema and full schema coverage, the description covers scope, use case, and return value (progress summary). It could note throttling or the superadmin-only path, but those are documented in the schema, leaving only minor gaps.

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 (force, limit, agentId, customerId) are fully documented in the schema itself. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema carries the burden.

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), resource (insights), and scope (all runs of an agent), which implicitly separates it from the single-run 'regenerate_run_insights' sibling. It is clear what the tool does, though it never names the sibling it contrasts with by name.

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 clear conditions for reaching for this tool. It stops short of naming alternatives (regenerate_run_insights, refresh_agent_insights) or stating when NOT to use it, so it is good but not complete routing guidance.

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