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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that — the four-list priority ordering, the next-item-first convention, and that includePool entries are matched to the person's role and level. It doesn't cover pagination or result-size limits, but it materially extends what the annotations provide.

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?

One dense paragraph, front-loaded with what is returned, then scoping rules, then the usage cue. Every sentence carries information, though the packing of list names and pool names into a single block is slightly heavy.

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?

No output schema exists, and the description compensates well by spelling out the four list names and their ordering plus the optional pool lists. It omits the shape of individual queue items and any size/limit behavior, so it is close to but not fully complete for a tool with no output schema.

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 the baseline is 3, but the description adds semantics the schema lacks: includePool pulls a shared 'any' pool (poolBugs/poolTasks) filtered by the person's role and level, and the priority/ordering meaning of the returned lists. userID's default-to-token-owner is already in the schema.

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?

Names a specific verb+resource and goes further by enumerating the exact return contents (urgentBugs, urgentTasks, bugs, tasks) and the exclusion of review/testing/approval items. An agent can distinguish this from task_search or task_context without opening a schema.

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 states the trigger context: 'Useful when the user asks what to work on next.' The exclusion note also implicitly routes agents away from this tool for review/testing/approval work. No alternative tool is named by name, so it stops short of a 5.

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