get_pull_request_checks

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

No annotations are supplied, so the description carries the full burden. It discloses output content ('pipeline and run identifiers') and implies a read-only summary, but never states that it is non-mutating, nor says anything about permissions, scoping to the default organization, or whether only the latest run per check is returned.

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?

Short and front-loaded: the purpose sentence comes first, then two supporting bullets. The clause 'so you can jump straight to the blocking validation' is mildly promotional, but no sentence is redundant or padding.

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 four-parameter, non-mutating read tool with no output schema, the description covers the purpose, the shape of what is surfaced, and the natural follow-up tools. What remains missing is minor: no mention of whether checks for non-latest commits are excluded, and no explicit read-only assurance.

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 organizationId, projectId, repositoryId and pullRequestId are already documented with defaults. The description adds no meaning beyond the schema — it never clarifies that repositoryId and pullRequestId are required or how ID vs. name is resolved.

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 ('summarize') and a specific resource ('latest status checks and policy evaluations for a pull request'), which cleanly separates it from get_pull_request and get_pull_request_changes. An agent can tell what this returns without opening the schema.

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?

Explicitly routes the agent forward: pair with get_pipeline_run and pipeline_timeline to inspect failures in depth, which names concrete alternatives. It gives clear positive context but no exclusions (e.g., when to use get_pull_request instead), so it stops short of a full when/when-not rubric.

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