bb_delete_pull_request_comment

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

No annotations provided, so description carries full burden. It discloses permanent removal (destructive), authorization requirement, and return value (confirmation with deleted comment id). This is transparent and sufficient.

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?

Very concise: one sentence for purpose, then behavioral details, then a bullet list of arguments. Every sentence adds value and is front-loaded. No wasted 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?

For a 4-parameter tool with 2 required, no nested objects, and an output schema, the description covers purpose, usage, behavior (authorization, permanence), parameter sourcing, and return value. Complete for effective usage.

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 coverage is 100%, so baseline 3. Description lists args in a docstring but adds little beyond schema—only repeats descriptions already in the schema. No additional semantic nuance provided.

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?

Description clearly states 'Delete a comment from a Bitbucket pull request.' This distinguishes it from sibling tools like bb_create_pull_request_comment and bb_edit_pull_request_comment.

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?

Explicitly specifies that only the comment's author can delete it and that deletion fails otherwise. Also tells where to get comment IDs (bb_get_pull_request_comments), providing clear when-to-use guidance.

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