Get a single task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It correctly indicates a read-only retrieval, but does not mention what happens for missing/invalid ids, authentication requirements, or the exact response shape.

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 front-loaded sentence with no redundant information. It communicates the essential behavior efficiently.

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?

For a simple single-task getter, the description is minimally adequate, but it lacks guidance on error behavior, response structure, and how it relates to sibling tools. Since there is no output schema or annotations, those gaps make it incomplete rather than fully sufficient.

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 0% and the only parameter 'id' has no schema description. The phrase 'by id' clarifies that the parameter is the task identifier, but it adds no detail about expected format, restrictions, or examples beyond what the property name already suggests.

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 clearly states the tool returns one task by id, with a specific verb and resource. It is distinguishable from the sibling sp_tasks_list, though it doesn't explicitly mention that distinction or other getter-like siblings.

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 implies this tool is for retrieving a single task when its id is known, but it gives no explicit guidance on when to choose this over sp_tasks_list or other task operations. Usage context is inferable, not stated.

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