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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating exactly what the record includes (sources, dates, verification levels, provenance citation, complaint-desk URL), which goes beyond the annotation metadata. No contradictions.

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 description is a single sentence that front-loads the main purpose and then lists the components in a structured, parenthetical manner. It is detailed but not padded; every clause adds relevant information. Slightly long, but appropriate for the complexity of the return payload.

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, the description does not need to define the return structure. It covers the full scope of what the tool returns, including provenance and the complaint-desk URL. Missing explicit error-handling or prerequisites, but for a read-only tool with one parameter, this is largely complete.

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?

The schema already provides full coverage (100%) for the single 'slug' parameter with an example, so the description adds no additional parameter-level meaning. Per the rubric, baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Return') and a precise resource ('one provider's full record'), listing the major components (tier, composite, coverage, pillar scores, indicator values, verdicts, flags, provenance). It differentiates from the sibling bank_index by explicitly limiting scope to a single provider.

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 implies when to use this tool (when you need one provider's full record) but does not explicitly mention alternatives like bank_index or search, nor does it state when not to use it. The context is clear but no exclusions or routing guidance is given.

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