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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description is free to spend its words elsewhere — and it does: it discloses the exact payload shape, the null-vs-zero semantics, the specific condition under which front_door_ai.score is null, and the per-call price. The main omission is any mention of rate limits, caching, or auth requirements.

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 core purpose is front-loaded in the first clause, and every subsequent clause (return contents, null semantics, pricing, price-sheet pointer) carries real information. It is dense and long for a single description, but no sentence is outright filler.

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, the description takes on the return-value burden and does it well by naming every field group the agent will get back, including the nested front_door_ai components and the null condition. What it lacks is the disambiguation an agent needs given the crowded family of rating tools.

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 100%, including a format example for slug that points back to find_providers, so the schema already carries the parameter burden. The description adds nothing about slug or the optional context field, which matches the baseline of 3 when the schema does the work.

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 names a specific resource and scope — one provider's full rating breakdown — and enumerates its components (composite, band, trend, six facets) plus two adjacent readings. It is clear what the tool returns, but it never contrasts itself with close siblings like get_provider_facets, get_rating_history, or find_ratings, which also return rating-related data.

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?

There is no statement of when to use this versus alternatives, even though the sibling list contains several overlapping rating tools (find_ratings, get_rating_history, get_provider_facets, get_agent_readiness). The only conditional content is a data caveat ("Null means no reading, not a zero") and pricing, neither of which is a usage rule.

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