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

Annotations already mark the call read-only and non-destructive, and the description adds useful behavioral context: the source methodology, a $0.02 USDC cost, and concrete example outputs. It does not contradict the annotations, and it discloses the return categories without specifying result formatting.

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 front-loaded with the use trigger, followed by output categories, a concrete example, source, and cost. It is slightly verbose because the example sentence carries illustrative numbers, but each component adds some value.

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?

The description covers the use case, high-level outputs, source, and cost, making it minimally viable. It is incomplete for an agent because the optional parameters are not explained and no output schema exists, so the expected response shape and parameter effects remain unclear.

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% and the description never explains how state, hospital_name, or current_star_rating influence the call. With three undocumented parameters and no required fields, the agent gets no guidance on whether to pass a filter or what the values mean.

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?

Description clearly identifies a specific resource (CMS Hospital Star Rating) and the actionable outputs: domain weights, national distribution benchmarks, and improvement priorities. It does not explicitly distinguish itself from sibling tools like get_hospital_care_compare_quality, so it falls short of full differentiation.

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?

Opens with an explicit 'Use when' condition covering strategy advice and benchmarking, which tells the agent when to invoke it. It offers no exclusions or named alternatives, so it stops short of full usage routing.

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