get_task

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

No annotations provided, so description must disclose behavior. It only states 'Returns: Task details from ClickUp API', missing important aspects like auth requirements, rate limits, and that this is a read-only operation. Does not mention error handling or response structure beyond vague '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 short (two sentences) and conveys the basic purpose, but lacks structure. It could benefit from clearly labeling sections like 'Parameters' and 'Returns' instead of inline text.

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 an output schema exists, the description need not detail returns, but it still provides a vague mention. It omits important context such as the dependency between custom_task_ids and team_id, and does not explain potential error scenarios. Adequate for a simple retrieval tool but not complete.

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 merely lists parameter names from the schema ('task_id, custom_task_ids, and team_id') without adding meaning. The schema already provides descriptions for these sub-parameters, so the tool description adds no additional value. With 0% schema description coverage at top-level, the description should compensate but fails.

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 'Get a specific task by ID', which is a specific verb-resource pair. It implicitly distinguishes from siblings like list_tasks (retrieves multiple) and update_task (modifies), but does not explicitly differentiate.

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 (e.g., list_tasks for multiple tasks). No mention of prerequisites or contextual conditions like requiring team_id when custom_task_ids is true.

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