boj_github_list_prs

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like authentication needs, rate limits, pagination, or response format. It lacks details on what 'list' entails, such as whether it returns all PRs or requires parameters for filtering.

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 description is extremely concise with just three words, making it front-loaded and efficient. However, it's under-specified rather than optimally concise, as it lacks necessary details for effective tool use.

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?

Given no annotations, no output schema, and 3 parameters with 0% schema coverage, the description is incomplete. It doesn't provide enough context for a tool that likely interacts with GitHub API, missing details on behavior, parameters, and output.

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%, so the description must compensate but adds no parameter information. It doesn't explain the meaning of 'owner', 'repo', or 'state' parameters, leaving them undocumented. With 3 parameters and low coverage, this is inadequate.

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 'List pull requests' states the verb and resource clearly, but it's vague about scope and doesn't differentiate from sibling tools like 'boj_github_list_issues' or 'boj_github_get_pr'. It specifies what it does at a basic level but lacks detail about what kind of listing it performs.

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 is provided on when to use this tool versus alternatives such as 'boj_github_get_pr' for a single PR or 'boj_github_list_issues' for issues. The description implies usage for listing PRs but offers no context about prerequisites, filtering, or comparison with siblings.

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