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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's one contribution beyond that is disclosing the aggregation in the result (application count per version), which is useful, but it says nothing about ordering, empty-state behavior, or how versions with zero applications appear.

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?

A single short sentence with no filler, and the payoff (per-version application counts) is placed after the resource. The leading fragment "The registry" is economical but ambiguous, which keeps it from a 5.

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?

For a parameterless read with no output schema, the description is only barely sufficient: it names the resource and one returned field, but leaves the return shape (version identity, resume linkage, ordering) unexplained. Given the simplicity of the tool this is adequate rather than complete.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The only semantic question left, what a 'version' is, is not addressed but is also not a parameter concern.

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 sentence implies a list operation over resume versions and adds that each entry carries an application count. But "The registry" is a vague noun with no explicit verb, and it never distinguishes this from hunt_get_resume or hunt_add_resume_version, so the agent must infer that this is the read/list sibling.

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 at all. With siblings hunt_get_resume, hunt_add_resume_version and hunt_pipeline in the same family, the description never says whether this is the listing view versus a single-version fetch or a write.

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