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

Annotations declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds useful context that it operates on *persisted* data and writes a new snapshot, confirming an overwriting mutation rather than a read. It stops short of describing what existing data is replaced or any re-computation cost, but it does not contradict the annotations.

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 sentences, zero waste: the action is front-loaded and immediately followed by the when-to-use routing. Every clause earns its place.

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?

Despite no output schema, the description notes the return value ('newly written snapshot'). Combined with the 100% schema coverage and annotations, an agent has everything needed to call and interpret this mutation correctly.

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%, so the schema already documents customerId, timeFilter, and regenerateFullInsights. The description adds no parameter syntax or semantics beyond the schema, which sets the baseline at 3.

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 (force-refreshes) applied to a specific resource (persisted fleet intelligence) and names the return value (newly written snapshot). This distinguishes it cleanly from the sibling read-only get_fleet_intelligence.

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?

Explicitly names the trigger conditions ('when get_fleet_intelligence reports stale or missing trend confidence') and an alternative scenario ('a recent ingestion needs the fleet-level report recomputed immediately'), and implicitly routes the agent away from the read tool. No inference required.

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