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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral context beyond them: CI failure shape with up to 8 file:line rows, log withholding when the credential cannot read logs, conflict-probe statuses, auto-merge wait reasons, and merge-train dequeue receipts. It does repeat "Read-only," but the surrounding detail earns credit.

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 purpose is front-loaded, but the bulk is a single dense sentence packed with semicolon-delimited output details. Those details are relevant because no output schema exists, yet the run-on structure makes the definition harder to parse than necessary.

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?

With no output schema, the description must explain return values, and it does so extensively. However, it completely omits input parameter semantics despite 0% schema description coverage, leaving a meaningful gap for correct invocation.

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 0% for owner, repo, and number, and the description never explains these inputs at all. Although the parameter names are conventional, the description does not compensate for the schema gap, making parameter meaning inferential only.

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 and resource: "Compute a one-shot status summary for a PR," then enumerates the status facets it combines. This clearly distinguishes it as a consolidated PR-status read tool, though it never explicitly contrasts with siblings like get_pr, get_pr_checks, or list_pr_conflicts.

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?

Offers no explicit when-to-use, when-not-to-use, or named alternative guidance. Only phrases like "one-shot status summary" and "Read-only" imply context, leaving the agent to infer when this is preferable to sibling status tools.

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