task_get

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

Declares read-only, no side effects, and explains parameter resolution (prefix matching). No annotations provided, so description carries burden. Could mention error cases or authentication, but still strong.

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 plus a brief Args line. Front-loaded with purpose, then usage, then safety note. Every sentence is essential and well-placed.

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?

Output schema exists, so return values need not be explained. Description lists included data (description, outcome, history, comments) and parameter behavior. Complete for a read tool.

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%, but description adds value by clarifying that short prefixes (min 4 chars) are resolved if unambiguous. This is beyond the schema description.

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?

Clear verb 'fetch', resource 'task', and includes 'chronological comment log'. Distinguishes from sibling task_list by specifying it returns full details and history.

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?

Explicitly says to use after task_list() provides an ID, and states what scenarios it fits (description, expected outcome, history). Also declares read-only nature, helping avoid misuse.

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