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

Annotations already set readOnlyHint=true, and the description adds meaningful behavior: it returns either a current snapshot or a historical daily series, requires Gold tier for history, and is updated quarterly. This goes beyond the annotation without contradiction.

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 sentences: the first front-loads the return value and key fields, the second lists specific use cases, and the third indicates update frequency. Each sentence earns its place with no filler or repetition.

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 purpose, exact data source, output field names, time-series limit, use cases, update cadence, and the history behavior. With no output schema, listing these fields compensates well, though exact response envelopes and data types are not specified.

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 description covers 100% of the parameter (days), including range, purpose, and tier behavior. The tool description does not add additional parameter meaning, so a baseline of 3 is appropriate.

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 clearly specifies a 0-100 US healthcare administrative-overhead gap index, names the data source (CMS Medicare), lists all output fields, and distinguishes this tool from the many numeric siblings by topic and scope.

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 explicitly lists when to call the tool ('hospital admin overhead, billing or payer friction, inpatient margin compression, RCM investments, provider-credit reviews') and states update frequency. It lacks when-not-to-use guidance or alternative tool names, but the provided triggers are highly specific.

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