get_task

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

With no annotations, the description must carry behavioral context. 'Get' implies a read-only operation and 'full detail' suggests a rich response, which is helpful. But it doesn't disclose auth requirements, not-found behavior, errors, or response shape beyond the vague phrase 'full detail.'

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 first sentence is appropriately concise and front-loaded, but the second sentence 'On v2 the description is Markdown' is extraneous and confusing. It does not help an agent select or invoke the tool, and should be removed.

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?

This is a simple single-parameter getter, so the core invocation is clear. However, there is no output schema, no guidance on when to choose this over similar task tools, and no mention of error behavior or what fields 'full detail' actually includes. It is minimally viable but not 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 schema has one required parameter, task_id, with 0% schema description coverage. The description does not explain task_id beyond the schema's own title 'Task Id,' and it doesn't add examples, constraints, or context about how the ID is obtained or used.

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 clear verb and resource: 'Get a single task with full detail.' This distinguishes it from list/search/update/delete siblings by scope ('single') and depth ('full detail'). However, it doesn't explicitly name a sibling it is not, and the second sentence about v2 Markdown is irrelevant to the tool's purpose.

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?

Usage is implied: use this tool when you need one task's full details rather than a list of tasks. But there is no explicit 'when to use' or 'when not to use' guidance, and no mention of alternatives like list_tasks or search_tasks.

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