get_task

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'Get' clearly indicates a non-mutating read operation, and 'full details' suggests the response will be comprehensive. However, it does not describe error behavior, missing-task handling, or the actual response structure.

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 one short, clear sentence with no wasted words. It is front-loaded with the action and resource, making it instantly scannable.

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 single-parameter getter with no output schema, the description is largely sufficient: it tells the agent the operation is a read and that the response contains full task details. It does not enumerate exact fields, but the context of sibling tools and the simplicity of the operation make this an acceptable level of completion.

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 100%, and the schema already defines taskId as a string with the description 'Task ID'. The tool description adds no additional parameter semantics beyond implying the task is identified by ID, so the baseline of 3 is 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 (Get) and resource (specific task), and 'full details' distinguishes it from the sibling list_tasks tool. The agent can tell this is a single-task retrieval by ID rather than a listing operation.

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 phrase 'specific task' implies that this tool is for retrieving one task by ID, which provides some guidance. However, it does not explicitly state when to use this instead of list_tasks, create_task, or update_task, nor does it mention any exclusions.

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