Get Task

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

No annotations are provided, so the description carries the behavioral disclosure burden. It conveys that the operation is a read that returns full task details, subtasks, and related notes, which is useful context, but it does not describe the response structure, potential absence of results, or any safety considerations.

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 a single, focused sentence that front-loads the core action and then adds the most relevant scoping details. There is no filler, repetition, or unnecessary qualification.

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 tool is simple with one parameter, but there is no output schema and no explicit description of the return format beyond 'full detail' and the mentioned sub-tasks/notes. The description is adequate for a basic retrieval action, but an agent would still lack clear expectations about the exact response fields or error behavior.

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 input schema has one required parameter, task_id, and its description is clear, so schema coverage is 100%. The tool description adds no extra meaning about how task_id should be interpreted, but the schema already covers the necessary semantics, making the baseline of 3 appropriate.

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 a specific verb and resource: 'Get full detail for a specific task,' and explicitly scopes the response to include 'sub-tasks and related notes.' This distinguishes it from sibling tools like list_tasks and get_next_tasks, which are broader list-type operations.

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 no guidance on when to use this tool versus alternatives such as list_tasks or get_next_tasks. There is no stated context, prerequisite, or exclusion, so the appropriate usage must be inferred from the name and generic wording.

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