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

The description states 'Read-only, merges and deploys stay a human tap,' but the annotations declare readOnlyHint=false, which asserts the tool may mutate state. This is a direct conflict on the single most decision-relevant trait for an agent. Cost context (3 MESH/call) is useful, but the safety claim cannot be trusted against the structured hint.

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?

Front-loaded and short, but the em-dash chain is dense and the aside '(3 MESH/call, a tool · ops)' is metadata clutter. 'A walk-around to claimed vs live' is awkward phrasing that costs a re-read.

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 no-output-schema tool the description does at least say the result is 'match or drift', but with an opaque nested input payload and a read-only claim that conflicts with annotations, an agent still cannot confidently construct the call or predict the effect.

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 is one required parameter, a generic 'input' object whose schema description only offers unrelated examples (agent-brain, agent-memory). The description says nothing about what payload this tool expects, so despite 100% nominal coverage the actual shape is opaque and the description does not compensate.

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 names a specific verb and resource and enumerates the three checks it performs (code head, running host, public site) plus the output (match or drift). That is far more specific than a sibling like tests-passed-check or pinned-repos-check, though it never names an alternative tool directly.

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 phrase 'with a walk-around to claim... where there is no repo' implies a usage condition (use it when there is no repository to anchor the comparison), but it is oblique and there are no explicit exclusions or named alternatives such as negative-check or mock verification tools.

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