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 output is 'normalized' and lists the failure states it handles, but does not explain the unusual idempotentHint=false on a read-only diagnostic or any rate-limit/return-shape behavior.

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 compact sentences with no filler; the trigger conditions come first and the outcome statement second. Efficient, though 'Get normalized connection health and diagnostics' is mildly redundant with the first sentence.

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?

An output schema exists so return values need not be described, and annotations cover safety. Still missing the disambiguation from get_connection_health and any meaning for account_id, which an agent needs to pick correctly and invoke confidently.

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 0% and the single parameter account_id is never mentioned or explained in the description. For a one-parameter tool the meaning is largely guessable, but the description does nothing to compensate for the total lack of schema documentation.

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 gives a specific verb ('get', 'diagnose') and resource ('normalized connection health and diagnostics'), so the agent knows it returns diagnostic output rather than raw data. However, it never distinguishes itself from the very similar sibling get_connection_health, leaving the two tools ambiguous.

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?

It states explicit trigger conditions: unhealthy, expired, scope-limited, or provider-review-limited connections. That is clear 'when to use' context, but there is no 'when not to use' and no pointer to get_connection_health as the alternative for the same domain.

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