get_task

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

Annotations already state readOnlyHint, idempotentHint, destructiveHint. The description reinforces these with 'Fetches data. Makes no changes' and adds the HTTP method and route. No contradictions. Adds useful context that it's for 'Deal Tasks'.

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 mostly clear but contains redundancy: 'Retrieve a task' appears twice, and 'Fetches data. Makes no changes' is already implied by annotations. Could be trimmed without losing meaning.

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 read tool with one parameter and no output schema, the description covers the essential context (task retrieval, read-only, endpoint). It omits what the response looks like, but that's acceptable given no output schema.

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 100% with a single parameter 'id' described as 'The ID of the task'. The description adds no additional parameter info beyond the schema, so baseline 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 clearly states the tool retrieves a task, is read-only, and uses GET. The verb 'Retrieve' and resource 'task' are explicit. The sibling tools include create_task, delete_task, update_task, and list_all_tasks, so this tool's purpose is distinct.

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 does not specify when to use this tool over alternatives like list_all_tasks or other retrieval tools. There is no guidance on prerequisites, context, or exclusions. The only hint is the parameter 'id', implying you need a specific task ID.

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