Are version, pin, and changelog targets consistent for release?

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description mainly reaffirms this with 'Read-only — never modifies files.' It adds the useful consequence that pin drift is silent otherwise, but does not disclose additional behavioral context beyond what annotations already cover.

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, each with a clear job: define the check, state when to use it, and reassure about side effects. The description is front-loaded with purpose and contains no filler.

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 zero-parameter, read-only, idempotent tool with an output schema, the description supplies everything needed to invoke it correctly: the exact verification scope and the usage trigger context. Nothing material is missing.

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?

There are zero parameters, and the instructions establish a baseline of 4 for such cases. The description still usefully clarifies what the parameterless check examines, even though the empty schema leaves no parameter meaning to supplement.

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 action—verify—and a precise resource scope: every version target, pin target, and changelog file, organized per version group. This clearly differentiates it from sibling tools like rrt_drift or rrt_sync_check by framing it as a release gate.

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?

The description gives explicit timing: use as a pre-release gate and after any edit touching a version string in docs or config. It does not name alternative tools or spell out when not to use, so it misses the explicit exclusion dimension for a 5.

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