get_pull_request_tasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states the resource and does not reveal important behavior such as pagination (limit/start), response format, or whether 'tasks' and 'blockers' are returned together.

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 a single short sentence that gets straight to the point with no filler or redundant information. It is appropriately sized for the simple purpose it conveys.

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 tool with five parameters, no output schema, and no annotations, the description is too sparse. It fails to explain what blockers are, whether tasks and blockers are distinct, or how the pagination parameters (limit/start) behave, leaving the agent with incomplete guidance for 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 100%, with all five parameters described in the input schema. The description adds no additional semantic meaning beyond the tool's purpose, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and a clear resource ('tasks/blockers on a pull request'), making the tool's function immediately obvious. It also distinguishes itself from sibling tools like get_pull_request and get_pull_request_activities, which retrieve different types of PR data.

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?

There is no guidance on when to use this tool compared to alternatives. It does not mention that it is the dedicated tool for PR tasks, nor does it contrast with related tools like get_pull_request_activities or list_pull_requests.

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