Mooring

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides minimal context. It doesn't mention pagination behavior, result limits, rate limiting, or authentication requirements that are relevant for GitHub API operations. The presence of an output schema is noted in context but the description doesn't hint at the return structure.

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?

Well-structured with the purpose statement front-loaded followed by parameter documentation. The Args format is slightly informal but perfectly readable. No redundant or wasted text - every line adds specific information not present in the schema.

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?

Adequate for a read-only list operation with an output schema present. However, given it's a list operation potentially returning many results, the description should mention pagination behavior or result limits. Missing safety/scope guidance (though 'List' implies read-only) given lack of annotations.

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?

Excellent compensation for 0% schema description coverage. The Args section documents all 4 parameters with meaningful semantics: 'repo' includes the owner/name format requirement, 'state' enumerates valid values (open/closed/all) and default, and filter parameters 'author' and 'label' clarify their filtering purpose.

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 clearly states 'List pull requests from a GitHub repository' with a specific verb and resource. However, it doesn't explicitly differentiate from the sibling tool 'gh_pr_detail' - it should clarify that this returns a collection/summary versus detailed information about a specific PR.

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?

No guidance provided on when to use this versus 'gh_pr_detail' (which likely returns more comprehensive information about a single PR) or versus 'gh_issues' (for issues instead of PRs). The agent must infer based on tool names alone.

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