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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the scope of coverage data (sources, last update, known gaps), but does not disclose behavioral traits beyond what annotations provide, such as default behavior when denomination is omitted.

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 dense sentence that efficiently lists the returned coverage fields without redundancy. It is appropriately sized, though the lack of a leading action verb makes the structure slightly less front-loaded than ideal.

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 one optional parameter and no output schema, the description adequately explains what the tool returns, including coverage scope, districts, run counts, sources, update date, and gaps. It omits any usage context or default-filter behavior, which is a minor gap for an informational read-only tool.

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%, so the single optional denomination parameter is fully documented in the schema with an enum and description. The tool description mentions denominations but adds no syntax, default, or filtering semantics beyond what the schema already provides, so the 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 identifies the resource (star note print run figures coverage) and enumerates the specific information it returns, which is clear enough to distinguish it from operational siblings like find_star_runs. It lacks a direct action verb and does not explicitly differentiate itself from check_serial or list_serial_patterns, but the resource focus is 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 guidance on when to use this tool versus alternatives such as find_star_runs or list_serial_patterns. The description only states what information is returned, leaving the agent to infer the appropriate context.

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