Get Pull Request Tasks

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds pagination behavior (defaults, max recommendations) and return structure (state, content, creator info). This enriches transparency beyond annotations.

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 concise with 7 lines: a one-line summary, a 5-line Args section, and a 1-line Returns section. Every sentence is useful and front-loaded, with no unnecessary words.

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 the tool's complexity (5 parameters, output schema exists), the description adequately covers parameters and return fields. It could be slightly more complete by explaining how pagination works across page_size and max_pages, but overall it provides sufficient context.

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 fully compensates by providing detailed explanations for all 5 parameters, including defaults and recommended limits (e.g., 'page_size: default 10, max recommended 100' and 'workspace: optional, defaults to configured workspace').

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 tasks on a pull request with pagination support.' It uses a specific verb ('list') and resource ('tasks on a pull request'), distinguishing it from sibling tools like get_pull_request_task (single task) and create/update/delete tasks.

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?

The description implies usage for listing all tasks with pagination via parameters like page_size and max_pages. However, it does not explicitly state when to use this tool over alternatives (e.g., get_pull_request_task) or provide conditions for when not to use it.

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