Get one TaskMarket task

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

With no annotations, the description carries the burden. It discloses that the record is 'live' and 'authoritative,' implying read-only behavior and contrasting with stale board scans. It doesn't mention error handling or whether the task is returned in full, but for a simple fetch tool, this is adequate.

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 the first stating purpose and the second providing a critical usage guideline. No filler words; every sentence serves a function.

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?

The description provides the essential information for a simple single-parameter fetch tool: what it fetches, when to use it, and why it's needed (staleness). It doesn't specify return format or error responses, but given the lack of output schema and the tool's simplicity, this is reasonably complete.

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 description mentions 'by id,' which ties the taskId parameter to its purpose, but adds little beyond the schema's existing type and minLength constraints. With 0% schema description coverage, the description only minimally compensates, though the parameter name is self-explanatory.

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 uses the specific verb 'Fetch' and identifies the resource as 'the live, authoritative record for one task by id.' It clearly distinguishes from sibling tools like search_tasks by focusing on a single task by ID.

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 explicitly instructs to 'Always re-fetch this immediately before acting on a task' and explains why: 'a board scan can be stale.' However, it doesn't explicitly name alternatives like search_tasks or state when not to use this tool, so it falls 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.