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

Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) establish a non-destructive write, and the description adds meaningful behavior beyond that: merged entries are stored and checked against a live external page, closed-without-merge fails, open ones wait, unrecorded PRs are ignored, and it is free. This is solid state-transition disclosure, though it doesn't explain permissions or error output.

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?

It is a single dense run-on sentence loaded with parentheticals and internal jargon. The behavioral outcomes are front-loaded-ish but readability suffers, and some phrasing ('one closed without merging fails') is ambiguous.

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 write tool with no output schema, it covers per-state behavior adequately, but omits what the tool returns, auth requirements, and how failures surface, leaving real gaps for an agent invoking it.

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 0% for the single 'prs' array. The description compensates by naming the source shape (url,state,mergedAt via gh pr list), which conveys the field meanings, but it doesn't restate required fields or item limits.

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?

States a specific verb+resource (record merges) and describes the source data (gh pr list output for claimed PRs). It uses internal jargon like 'Claimed PRs Shipfound cannot see' and doesn't name sibling alternatives, but the core operation is identifiable.

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 implies the context ('for the Claimed PRs Shipfound cannot see', referencing confirm.prs and today), which gives some when-to-use framing, but never explicitly says when to prefer this over siblings like repo_confirm, verify, or shipped.

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