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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context — that results are ranked by impact and that badges indicate Converra-deployed fixes — but says nothing about scoping, pagination, result volume, or freshness, which matter for a fleet-wide aggregation tool.

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?

Front-loaded with the resource definition, then supported by concrete output details, then scenario questions. The example-question sentence is slightly padded but earns its place by mapping to real user phrasings; overall there is little waste.

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 readOnly annotations, a single optional parameter, and no output schema, the description is nearly self-sufficient — it explains what the returned data contains and how fixes are signalled. The remaining gap is sibling disambiguation against the other fleet/insight tools, which is not addressed.

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% and there is only one optional parameter (customerId, superadmin-only), so the schema carries the parameter burden adequately. The description does not mention the customerId parameter or its superadmin restriction, but baseline 3 is appropriate when the schema is fully documented.

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 resource — fleet-level failure patterns with business impact descriptions and fix verification status — and enumerates the concrete content (before/after failure counts, 'Improved'/'Fixed' badges). It's clear what it returns, but it never distinguishes itself from close siblings like get_fleet_overview, get_fleet_timeline, or get_insights, which an agent could easily confuse it with.

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?

The three example questions ('what are the biggest issues hurting my fleet?', etc.) give implied usage context and make the intended scenario fairly obvious. However, there is no explicit when-not guidance and no sibling is named as an alternative, so the routing decision against get_fleet_overview or get_insights is left to inference.

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