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

No annotations are provided, so the description carries the full behavioral burden. It discloses that output is aggregate-only and includes denominator and sample provenance, but says nothing about permissions, computation windows, rate limits, or how the rate is derived. The read-only nature is only inferable.

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?

One dense sentence with no filler, and the output content (denominator, provenance) and scope constraint ('Aggregate only') are front-loaded. It is telegraphic to the point of being terse, but every clause carries information.

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 annotations, no output schema, and a completely undocumented parameter, the description leaves too much to inference for an agent to call the tool confidently. It hints at return values but omits the population definition, parameter semantics, and any usage context.

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% for the single parameter gap_class, and the description only echoes it via 'per gap class' without defining valid values, format, or what happens when it is omitted (the parameter is not required). It does not compensate for the coverage gap.

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 resource (absence rate) and its unit of measure (per gap class for a population), and explicitly notes the output includes denominator and sample provenance. The action verb is only implied ('Measured'), and there is no differentiation from the siblings, but the resource and scope are unambiguous.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as bulk_export or host_report. The phrase 'Aggregate only' is a scope limit rather than routing guidance, so an agent has no stated condition for preferring this tool.

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