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 covered structurally. The description still adds real behavior beyond them: the 24-hour look-back window, hold expiry and renewal semantics, heartbeat tracking, and the guarantee that it never fails but reports why reads failed. That is meaningful added context over the annotations.

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 first sentence front-loads the trigger and purpose, and subsequent sentences cover filtering, return fields, and the read-only boundary. Every sentence carries information, though the long middle sentence packs the return shape into a dense clause list that could be tightened.

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?

There is no output schema, so the description must describe return values itself, and it does: operation, holder, since, until, heartbeat, plus the 24-hour window. It also covers failure behavior and the read-only constraint, leaving nothing an agent needs before calling.

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 baseline is 3; the description earns above that by explaining the effect of each parameter ("Give operation to ask about one", "For a repository it lists the operations") and by giving example operation identifiers (deploy:production, restart:api) that illustrate the namespaced pattern. It does not restate the repo fallback rule in detail, but the schema covers it.

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 opens with a specific verb-and-resource statement ("see whether another agent is already doing it" for a shared operation) and spells out the return shape: operation, holder, since/until, heartbeat. It is clearly distinguishable from claim-oriented tools. It does not differentiate itself from the similarly named sibling who_holds, which is the one ambiguity it leaves open.

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?

It states exactly when to call ("before you start a shared operation such as a deploy or a restart"), what to do with a positive result ("wait for them rather than starting it again"), and where claiming lives instead ("Operations are claimed with the agent pack's op-claim... this tool only reads them"). Both the trigger and the not-this-tool boundary are explicit.

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