Create Pull Request Task

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

Annotations (all false) provide no behavioral hints, and the description only states 'Create' without elaborating on idempotency, side effects, or required permissions. No additional context beyond the basic operation.

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 brief with a one-sentence summary followed by a structured Args/Returns list. It is efficient, though the Args section could be more compact; still, no unnecessary content.

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?

While the description covers parameter meanings and return type, it lacks context on error conditions, required permissions, or behavior when the PR or comment does not exist. The output schema exists but the description's 'Created task details' is vague. Adequate but with gaps.

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?

Despite 0% schema coverage, the description's Args section adds meaningful descriptions for each parameter (e.g., 'Task content in markdown format' for content). All 5 parameters are explained, compensating for the schema's lack of descriptions.

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 the action ('Create') and the resource ('a task on a pull request'), with the optional linkage to a comment. It distinguishes from sibling tools like delete_pull_request_task or update_pull_request_task by focusing on creation.

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 on when to use this tool versus alternatives (e.g., update_pull_request_task for modifications). No mention of prerequisites like write access or that the PR must exist.

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