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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description nonetheless adds real behavioral context by disclosing that omitting task_id switches the tool from a single-record fetch to a board listing, and that visibility is limited to poster and worker. It does not mention pagination or result limits on the board listing.

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 compact clauses, front-loaded with the primary fetch behavior and immediately followed by the alternate mode and its filters. No filler, though the visibility clause is compressed to the point of ambiguity.

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?

With no output schema and 0% parameter coverage, the description is the main source of semantics; it covers both operating modes and the filter names, which is the essential skeleton. It omits what fields a task detail returns, how the board listing is ordered or paginated, and the units for min_reward — meaningful gaps for a dual-mode tool.

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 does explain the semantics of omitting task_id and identifies category and min_reward as board filters. But it gives no unit or format for min_reward and no meaning for the many enum categories beyond their names, leaving gaps the schema cannot fill.

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 resource (task details) and adds a second, distinct mode: listing the open board when task_id is omitted. It carves out a role relative to siblings like my_tasks and next_task by scoping visibility to poster and worker. The phrase 'input/output visible to poster and worker' is terse and reads as a permission note rather than a purpose statement, so it stops just short of 5.

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 does explain the branch condition — omit task_id to list the open board — and names the two filters available in that mode. However, it gives no guidance on when to use this versus my_tasks, my_responses, next_task, or search_listings, so the agent must infer the intended context.

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