tasks get task

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered externally. The description adds nothing beyond that: no mention of error behavior for unknown ids, whether a missing tasklist falls back to @default, or what the response contains. Even with output schema present, the near-zero contribution from the text keeps this low.

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?

It is a single front-loaded sentence with zero waste, but for a tool with 0% schema coverage it is undersized rather than appropriately sized. Conciseness is fine; specification is not.

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 a simple read with an output schema and rich annotations, so much of the burden is offloaded. However, the undocumented tasklist_id parameter and its @default fallback leave a genuine gap an agent must guess at.

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 description coverage is 0%, so the description must carry the burden, yet it only hints at task_id via 'by id'. The second parameter, tasklist_id, with its '@default' value, is completely unexplained and an agent cannot infer its role or format.

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 verb and resource ('Get one task by id'), which lets an agent distinguish a single-item fetch from the sibling list tool tasks_list_tasks. It does not name the sibling or state the contrast explicitly, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus tasks_list_tasks or how to obtain a task_id. Usage is only implied by the name and the word 'one'.

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