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

With no annotations, the description carries the full behavioral burden. It mentions 'immutable' (history cannot be changed) and 'evidence-gated' (rollback requires evidence), which are useful traits, but it does not clarify whether the tool mutates state, what evidence is needed, whether rollback is destructive, or what permissions are required.

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 sentence with no wasted words, but its brevity comes at the cost of clarity and structure. It front-loads 'Return' but does not separate the two distinct functions it implies.

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?

Given the complexity of release flows and rollback operations, the description is far too sparse. It omits key information about the required 'slug', return values, evidence-gating mechanics, and whether the tool is read-only or mutating.

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 description coverage is 0%, and the sole parameter 'slug' has no description in either the schema or the tool description. The description adds no meaning about what the slug represents (e.g., flow ID, release ID).

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 verb ('Return') and resources ('version history', 'rollback operations'), but it is ambiguous whether the tool actually performs rollbacks or merely returns information about them. It does not differentiate itself from the many sibling tools like release_readiness or publishing_contract.

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?

No guidance is given on when to use this tool versus alternatives such as release_readiness or certification_replay. The description provides no context, prerequisites, or exclusions for invocation.

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