task_get

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

The description says 'Fetch a single task,' implying a read operation, but does not explicitly state that it is read-only, nor mention any side effects or requirements. With no annotations, the description should disclose more behavioral details.

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 very concise (4 words) with no wasted words. However, it is under-specified; a slightly longer description would improve clarity without losing conciseness.

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?

Given 3 parameters and no output schema, the description is incomplete. It does not explain the return value, parameter constraints, or any context about the task object. The tool's simplicity does not excuse the lack of essential details.

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?

The description does not explain the parameters (account, task_id, tasklist_id). With 0% schema description coverage, the description must compensate, but it provides no extra meaning beyond parameter names.

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 'Fetch a single task,' which clearly indicates the verb and resource. It distinguishes from siblings like task_list (list multiple tasks) and task_create. However, it could be more specific about the task context.

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?

No guidance on when to use this tool versus alternatives like task_list. The description lacks explicit usage context, such as when to fetch a single task vs. listing all tasks.

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