clickup_template_list

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

No annotations provided, so the description must carry the full burden. It states the return type (array of template objects) but does not disclose behavioral traits like read-only nature, authorization requirements, or pagination behavior beyond what the schema provides. Adequate but not rich.

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?

Three sentences, no wasted words. First sentence states purpose, second explains what templates are and links to the apply tool, third specifies return format. Front-loaded and efficient.

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?

No output schema, so the description must explain return values. It does so minimally ('Returns an array of template objects (id, name)'), but lacks details on whether the array is the complete result or paginated, and does not mention other possible fields or metadata. Sufficient for a simple list but not comprehensive.

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% (both parameters have descriptions). The description adds value by explaining the source of team_id ('Obtain from clickup_workspace_list') and clarifying pagination ('Zero-indexed page number... up to 100 templates'), which goes 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?

The description clearly states the tool's purpose: 'List the task templates available in a workspace.' It uses a specific verb ('List') and resource ('task templates'), and distinguishes itself from sibling tools by mentioning the apply action and specifying the scope ('in a workspace').

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 implies usage (list templates before applying via clickup_template_apply_task), but it does not explicitly state when to use or when not to use. No alternatives or exclusions are mentioned, leaving the agent to infer context.

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