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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds real substance beyond that — bots are excluded from reviewer suggestions, merged work carries 'hours waiting', blockers are categorized into five named states. It also gives an output-consumption instruction ('lead with the `headline`'), which no structured field conveys.

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?

Two sentences, front-loaded with what the agent gets, then a compact rendering instruction. Despite being dense with enumerated content, every clause maps to a distinct capability (blockers, reviewer queue, undeployed work, recent ships) rather than restating the name.

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 values need not be explained, and the description goes further by telling the agent how to relay the result. Scope, bot exclusion, and the four data sections are all covered; only the session-binding behavior when `repository` is omitted is left entirely to the schema.

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% and both parameters are described in detail in the schema (owner/name slug semantics, default 2 days, clamped to 1-30). The description adds nothing about either parameter, so the baseline 3 applies — the schema is doing all the work here.

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 — a personal, cross-repo status rollup — and enumerates exactly what it bundles: your open PRs with blocker reasons, unblockable reviews, merged-but-undeployed work, and recent shipments. That composition makes it clearly distinct from point tools like get-open-pull-requests-tool or get-merged-pull-requests-tool, though it never names a sibling to sharpen the boundary.

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 'standup prep and morning brief in one call' gives a concrete usage context that tells the agent when this aggregate is the right entry point. However, it offers no exclusions or routing advice — an agent drilling into one PR or one repo isn't told to prefer get-open-pull-requests-tool or get-peull-request-metrics-tool instead.

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