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

With no annotations, the description carries the behavioral burden and does so well: it discloses long-polling behavior, the 55-second maximum wait, and the incremental sync semantics of since_* fields. The read-only nature is implied by 'Fetch' and the descriptive return fields, though it does not cover timeout behavior or explicitly guarantee no side effects.

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 description is two sentences with no filler: the first sentence states the resource and return fields, and the second packs in the parameter behavior. All information is front-loaded and earns its place.

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?

Given that there is no output schema and no annotations, the description covers the main return fields and all non-obvious parameters well. It is missing explicit timeout/error behavior and precise since_status value formats, which would make it fully self-contained.

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 only 20% (api_key is documented), and the description compensates by explaining wait_seconds, since_status, and since_messages in meaningful, actionable terms. task_id is left implicit as the obvious required identifier, and the exact format of since_status is not specified, so it is not a perfect 5.

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 opens with a specific verb and object ('Fetch one of your tasks') and enumerates the expected payload: status, submissions with per-criterion evidence and attachment URLs, message thread, and an advice field. The 'one of your tasks' phrasing differentiates it from the listing sibling octopus_my_tasks and from mutation tools like octopus_approve or octopus_cancel_task.

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 clear operational guidance: use wait_seconds to block until the status moves or a new message arrives, and pass since_status/since_messages from the last look for incremental polling. It does not explicitly name when not to use the tool or contrast it with siblings, 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.