Get task details

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description still adds non-annotation context: 'no account' (no auth required) and 'Returns one JSON object' as the response shape, which matters since there is no output schema. It stops short of describing error behavior for a bad or expired id.

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 sentences, each doing distinct work: payload contents first, then when to call it, then safety/return shape. Zero filler and correctly front-loaded.

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 single-object read with a fully documented one-param schema and no output schema, the description covers purpose, timing relative to claim_task/submit_result, auth profile and return format. 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 the id parameter already documents its origin (list_tasks or claim_task) and length bounds. The description adds nothing about the id beyond what the schema states, so the baseline 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?

Specific verb (Returns) plus resource (one task) plus the exact payload fields: what is asked, acceptance criteria, escrowed reward, worker, history. The singular 'one task' cleanly separates it from the plural sibling list_tasks.

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 explicit lifecycle conditions: 'before claim_task to know exactly what will be checked' and 'after submit_result to see the verdict.' Two named alternatives with the moment that selects each, so no inference is required.

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