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

Annotations already establish that this is a safe, read-only, non-destructive operation. The description adds rich context beyond annotations by spelling out what is returned, including plan clauses, flow and people names, recent runs, allowedSites, and refused sites.

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 front-loaded with the core purpose and every clause describes relevant return content or usage. It is somewhat dense and run-on in the first sentence, but no sentence is wasted.

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?

Because there is no output schema, the description carries the burden of explaining return values, and it does so thoroughly. Combined with the usage guidance and annotation safety profile, an agent has enough information to call this read tool correctly.

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%, so both taskId and workspace are already documented in the schema. The description usefully notes that taskId comes from workbench_tasks_list, but it adds little about workspace semantics or value formats beyond what the schema provides.

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 'One Task in full' and explicitly enumerates the task sentence, status, latest saved plan, recent runs, allowedSites, and refused sites. That makes the verb/resource and scope clear enough to distinguish it from list, create, update, and compile siblings.

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 states exactly when to use it: before editing a task's sentence via workbench_tasks_compile, and when the user asks what a task does. It also tells the agent where to get the required taskId from workbench_tasks_list.

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