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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false). The description goes beyond them by disclosing the return content — assigned tasks, claimed tasks, and a count of finished work awaiting the human — plus the decision signal it surfaces. No return format/pagination detail, but with annotations the bar is lower.

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?

It is front-loaded with the core framing, but drifts into normative coaching ('the honest answer is to help clear it rather than start something new') that repeats the same point across three clauses without adding call-relevant information.

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 zero-required-param, read-only query tool with no output schema, the description needs to sketch the return shape — and it does, covering assigned tasks, claimed tasks, and the finished-work backlog. It is complete enough to call correctly, with only return formatting left implicit.

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 100% and the single 'limit' parameter is fully documented with bounds and a default, so the schema does the work. The description adds no syntax or format meaning beyond it, making the baseline 3 correct.

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 verb+resource: it returns the tasks assigned to you, what is currently claimed, and the volume of finished work waiting on the human. This is clear and distinguishes it from board-wide reads, though it never names the sibling tools (get_board_state, list_tasks) it is implicitly contrasted with.

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?

It gives implied usage — 'Ask what you should be doing, rather than reading the whole board and guessing' and 'if that queue is full... help clear it rather than start something new.' But it routes by describing behavior rather than naming an alternative tool, so the agent must infer that get_board_state is the thing to avoid.

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