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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are 'aggregated' and derived from run data, which hints at computed rather than raw values, but says nothing about staleness, caching, or whether a refresh is needed to see new insights.

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?

A single efficient sentence with no filler, and the core noun (aggregated performance insights) is front-loaded. It is arguably too terse given the crowded sibling space, but there is no wasted text.

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 read-only aggregation tool with no output schema and fully documented parameters, the minimum is met by the annotations plus schema. Still missing is the relationship to refresh_agent_insights / batch_regenerate_insights and any indication of what the aggregate contains, which an agent would need to choose correctly among the many insight siblings.

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%: agentId, days (with default 30), and the superadmin-only customerId are all documented in the schema. The description adds no extra parameter semantics, 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 and resource ('Get aggregated performance insights') scoped to 'an agent' derived from 'run data', which is clearer than the bare title. However it never differentiates itself from close siblings like get_run_insights, refresh_agent_insights, or get_fleet_intelligence, leaving the agent to infer the level of aggregation.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as get_run_insights (per-run) or refresh_agent_insights (to regenerate). The agent must guess which insight-fetching tool to pick from a list of several.

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