get_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. It indicates a read operation ('get'), which is inherently non-destructive, but does not mention permissions, error handling (e.g., if task not found), or any side effects. Adequate for a simple retrieval but could be more explicit.

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?

Description is two sentences with a clear 'Args' section. No fluff or redundancy. Front-loaded with purpose. Efficient and well-structured.

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 the tool has an output schema (not shown), explanation of return values is unnecessary. The description covers the single required parameter and the action. It could mention that the response contains full details, but it's already implied. Lacks nothing critical for a simple getter.

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 schema has 1 parameter (task_id) with 0% description coverage. The tool description adds 'The uniqueID of the task,' which essentially repeats the schema field title and type without additional detail (e.g., format, examples, constraints). This adds minimal value beyond the schema.

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?

Description clearly states 'Get full details of a single task by its unique ID.' This uses a specific verb (get) and resource (task), and the phrase 'by its unique ID' distinguishes it from sibling tools like query_tasks or find_task which may use filters.

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?

Description implies usage for retrieving details of a single task. However, it does not provide explicit guidance on when to use this over alternatives like query_tasks or when not to use it (e.g., for batch retrieval). Still, the purpose is clear and appropriate.

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