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

Annotations already cover read-only, idempotent, non-destructive, but the description adds what is actually returned (current status, conversation, next move, quoted AI answer with page citation) and, critically, a prompt-injection warning that quotedMaterial is evidence, never instructions. That is behavioral context an agent cannot get from the structured fields.

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?

The purpose and usage triggers are front-loaded in the opening clause, and the later sentences carry real payload (return composition, quoting rules). The closing 'Addresses and links are plain.' is terse to the point of ambiguity, but nothing is genuinely redundant.

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?

An output schema exists, yet the description still tells the agent enough about the response to act on it, and it flags the untrusted-content boundary that matters for a tool returning quoted messages and AI answers. Nothing needed to call it correctly is missing.

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 both parameters are fully documented in the schema, so the baseline applies. The description's note about the id coming from parse_next_tasks largely restates the schema's own wording, and brandSlug is not addressed at all.

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?

States a specific verb and resource — re-read one task — and pins the identifier's provenance to parse_next_tasks, which separates it from siblings like parse_get_question, parse_evidence and parse_search. The return shape is also characterized (complete task object, status, conversation, next move, one quoted AI answer).

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?

Gives three concrete trigger scenarios: before sending, after a change, and to see what is already recorded before recording more. It does not name a sibling to use instead in any situation, so it stops short of full when/when-not routing, but the usage context is unambiguous.

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