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

With readOnlyHint already covering the safety profile, the description adds real value by disclosing the data source ('read from git and CI rather than a handoff doc') and the full composition of the response (summary, blockers, per-workflow CI, PR grouping, merged window, queue). Since there is no output schema, this return-value disclosure is genuinely useful, though it restates 'Read-only' from 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 single sentence is long and comma-heavy, but the key orientation cue ('Start here when picking up work') is front-loaded and each clause enumerates distinct returned fields rather than padding. 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?

For an orientation tool with no output schema and only readOnly annotations, the description fully covers what an agent needs: what it reads from, every returned section, the recent-merge window, and the read-only nature. Nothing essential to correct invocation is missing.

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 owner, repo, and merged_since_hours are already documented in the schema. The description only reinforces merged_since_hours with its default (48), adding no syntax or semantic detail beyond the schema. Baseline 3 applies.

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 concrete resource ('the live state of a repository') and a clear role ('start here when picking up work'), and it enumerates the contents so an agent knows exactly what it returns. It distinguishes itself from a 'handoff doc' but never differentiates from nearby siblings like repo_health or pr_status_summary, so it stops short of a 5.

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?

'Start here when picking up work' gives explicit usage context and the contrast with a handoff doc clarifies the intent. There is no when-not guidance and no named sibling alternative, so it is clear context but not full routing guidance.

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