Get a task by id

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds further behavioral context: missing ids return task_not_found, and auth is via tool policy gate. It also clarifies the return payload contents (status, progress, result, error), which are not in the schema.

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 tightly packed sentences with zero redundancy. The main purpose is front-loaded, usage guidance follows, and behavioral details are summarized at the end. Every clause adds distinct value.

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-parameter read-only tool, the description fully covers what an agent needs: how to call it, when to use it, what it returns, what happens for missing ids, and the auth requirement. The annotations cover safety and idempotency; no output schema is needed because the payload content is described.

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?

The only parameter, task_id, already has a clear schema description ('Task id returned by tasks_create / tasks_list'). The tool description adds little beyond using the same term, so the schema carries the semantic load. Baseline 3 applies since schema coverage is high.

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 states a specific action ('Fetch one task handle by task_id') and names exactly what the handle contains (status, progress, result, error). It explicitly differentiates from sibling tools tasks_stats and tasks_list, so an agent can immediately distinguish it.

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?

The description gives explicit when-to-use ('poll after tasks_create') and when-not-to-use ('Do not use for aggregate counts — that is tasks_stats — or to list many tasks (tasks_list)'). It names the alternatives directly, leaving nothing to inference.

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