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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds real behavioral value by enumerating the returned dataset (scores, run counts, failure rates, deployment stats), which matters since no output schema exists; it does not mention pagination or volume limits.

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?

The payload summary is front-loaded in the first sentence and the example questions are compact. The three-question list is slightly redundant with the opening statement but still earns its place by clarifying intent.

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 present, the description correctly takes on the burden of describing the return contents, and the annotations cover the safety profile. The only meaningful gap is that it doesn't distinguish this aggregate view from the other fleet-level tools an agent could pick instead.

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 both parameters (sortBy with its enum and customerId) are already fully documented in the schema. The description contributes nothing about sorting semantics or the superadmin scoping requirement, so the 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?

The description states a specific verb+resource ('fleet-level dashboard showing all agents') and enumerates the metrics it exposes (performance scores, run counts, failure rates, deployment stats). It positions itself as the 'entry point' for fleet health, which helps, but it never names or contrasts with near-neighbors like get_fleet_intelligence, get_fleet_timeline, or list_agents.

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?

Concrete usage context is provided via the target questions it answers ('how are all my agents doing?', 'which agent needs attention?', 'what has Converra fixed?'), which clearly frames the when-to-use scenario. There are no explicit exclusions or named alternatives, so an agent must still infer that per-agent deep dives belong to get_agent/analyze_agent.

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