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

Annotations already establish that this is a non-read-only, non-destructive, idempotent operation. The description adds useful behavioral context: it returns a task that must be claimed/started and explicitly completed to resolve the finding, and it mentions 'reusing active work' as a side-effect nuance.

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?

Two sentences with no filler. The first sentence conveys the core action and scope; the second covers required follow-up behavior. The flow is a little dense but acceptable for the information provided.

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?

Without an output schema, the description should explain what the returned task looks like and how to complete it, but it only says 'claim/start the returned task' without specifying the task type, queue mechanics, or how the completion is performed. The meaning of 'reusing active work' and the roles of projectId and idempotencyKey are also left unstated.

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 must compensate. It implicitly clarifies findingId (the bug to fix) and vaguely references active work possibly tied to sessionId/executionId, but it leaves projectId and idempotencyKey completely unexplained.

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 states a specific action ('Queue a fix') and resource ('open Reports bug'), and clarifies that it targets a finding. It distinguishes itself from bug creation or report generation, though it doesn't name sibling tools explicitly.

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 provides clear context: use it for open Reports bugs while reusing active work. It also gives follow-up instructions (claim/start the returned task, complete as resolved), but doesn't explicitly mention when not to use it or name alternatives.

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