bitbucket_pull_request_task_create

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

Annotations mark the operation as read/write and non-idempotent, and the description goes further by disclosing that the created task remains pending and invisible to everyone else until the user's review is submitted. This is material behavioral context not covered by the annotations. No contradiction.

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?

A single, front-loaded sentence that conveys the core action and the key behavioral caveat without fluff. The dash construction is efficient and immediately communicates the most important constraint.

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?

Provides useful behavioral context and is short, but the unlinked parameter semantics (notably id) remain an obstacle to correct invocation. For a tool with 50% schema coverage and no output schema, this is a meaningful gap, though the rest of the context is present.

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?

Only repoSlug and workspace have schema descriptions; id and content are undocumented. The description adds no explicit meaning for these parameters, leaving ambiguity about whether id is the pull request ID or a task ID and what format content should take.

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?

States a specific verb ('Add'), resource ('checklist task to a pull request'), and a unique behavioral constraint ('pending - invisible to everyone but you until you submit your review'). This clearly distinguishes the tool from sibling task listing tools and leaves no doubt about the action.

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?

Gives a clear context for when the task is useful (before review submission), but never explicitly says when to choose this over alternatives such as bitbucket_pull_request_task_list or when not to use it. The usage is implied by the verb and subject rather than stated directly.

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