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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false). Beyond that, the description usefully discloses that aliases resolve to a canonical assessment and that an optional need runs a 'bounded editorial judgment over that assessment only' — real behavioral context. It stops short of describing rate limits, caching, or failure modes, so not a full 5.

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?

Three tight sentences, front-loaded with the core action before the editorial caveat and the need parameter note. Little wasted text, though the 'not an AM Best rating or a recommendation' clause is a slight detour.

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 an output schema present, return values need no explanation, and the read-only annotations cover the safety profile. The description adds aliasing behavior and the semantics of need, leaving only provider-identifier format as an unaddressed detail.

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 0%, so the description must carry parameter meaning. It does explain the effect of the optional need argument and that provider aliases resolve to a canonical record, but it never clarifies accepted provider formats (name, alias, ID, domain) despite minLength/maxLength constraints in the schema. Partial compensation only.

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 (Retrieve) and resource (a published reliability assessment and Reliability Score) scoped to 'one provider', which cleanly separates it from the multi-provider siblings search_provider_reliability and compare_providers. An agent can identify the operation without opening the schema.

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 description explains what the score is (editorial, not an AM Best rating) but never states when to use this tool versus the sibling search_provider_reliability or compare_providers, nor any prerequisite conditions. No when/when-not guidance is present.

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