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

Annotations cover readOnly and idempotent, so safety is already handled, but the description adds real behavioral detail beyond them: bots are excluded from the reviewer queue, recent merges default to a 2-day window, and the result should be relayed starting from the `headline` field. That is useful, non-obvious context for interpreting and presenting the 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?

The core noun phrase is front-loaded and the long parenthetical enumerates exactly what counts as each blocker state, which is high-value rather than filler. The final directive sentence is terse and actionable. It is dense but nearly every clause earns its place.

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?

An output schema exists, so return shape need not be re-explained, and annotations cover the safety profile. The description still supplies the section breakdown and the 'lead with headline' presentation rule, leaving nothing an agent needs in order to call and relay this tool correctly.

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 100%, so both parameters are fully documented in structured data, including the 1-30 clamp and the default. The description does not add any parameter-level meaning (no mention of repository binding or window sizing), so this sits at the baseline 3.

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 resource and scope ('Your personal cross-repo status') and then enumerates the exact sections returned: your open PRs and blockers, reviews you could unblock, merged-but-undeployed work, and recent ships. It is clearly distinguishable from siblings like get-open-pull-requests-tool or get-merged-pull-requests-tool because it is the aggregated personal composite rather than a single-list query.

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?

Gives an explicit use context — 'standup prep and morning brief in one call' — which tells the agent when this tool is the right pick over narrower siblings. It stops short of naming alternatives or stating when not to use it, so it earns a 4 rather than a 5.

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