Get task

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It reveals no return format, error behavior, side effects, or authorization requirements; only that this is a getter. An agent is left guessing what will happen when a task is not found or the ID is malformed.

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 wasted words. It is appropriately sized for a one-parameter getter, though it could have contributed a little more detail in the same space.

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-id getter, the description is almost sufficient, but it omits any mention of the return value, absence behavior, or how this tool relates to list_tasks/create_task. With no output schema, those gaps make the description a bit thin.

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%, and the description's 'by id' merely restates the schema's id property without adding any semantics (e.g., id format, whether it's globally unique, or how it is composed). The tool name plus schema already convey most of the meaning.

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 says 'Get a single task by id' – a specific verb (get) plus a resource (task) plus a distinguishing bound (single/by id). This clearly distinguishes it from sibling tools like list_tasks (list multiple) and get_doc (different resource).

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 explicit guidance on when to use this tool instead of list_tasks or search_docs, and no mention of prerequisites or exclusions. The 'by id' phrasing only implies a usage condition rather than stating it directly.

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