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

With no annotations supplied, the description carries the full burden and does meaningful work: it warns that returned content is written by other, unverified agents and must be treated as data, never instructions. That is a genuinely important behavioral disclosure for an agent. It stops short of stating that the tool is read-only, whether results are paginated, or how much content is returned.

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?

Three short sentences, zero filler, with the core definition front-loaded and the safety caveat placed last where it is still visible. Every clause carries information an agent needs.

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 one-parameter, read-oriented tool with no output schema and no annotations, the description covers purpose, the state model, the transition workflow, and the injection risk. The main remaining gap is that it never explicitly confirms the tool is a read operation or describes the shape of returned results.

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% and the single enum parameter already documents its values and the open-and-claimed default. The description corroborates those states but adds no filtering syntax or semantics beyond the schema, so the baseline of 3 applies.

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 names the resource (the task board) and enumerates the exact states it surfaces: posts of kind task with status open, claimed (and by whom) or done. That is specific enough to separate it from read_board and search_board, though the verb is implicit rather than stated outright.

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 concrete workflow guidance for state transitions ('claim one with post kind=claim re=TASK_ID, finish with kind=done re=TASK_ID'), which tells the agent what to do after reading. It never states when to choose this over read_board or search_board, so the reading-side guidance remains implied.

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