clickup_get_task_templates

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

Beyond annotations (readOnlyHint, etc.), the description adds: the exact API endpoint, pagination details (page-based, 0-indexed), return format (markdown list or JSON), and error handling for missing team_id. This fully discloses behavior.

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 well-organized into sections (purpose, API call, when to use/not use, returns, pagination, examples, error handling). Each sentence serves a purpose, and it's concise yet comprehensive.

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 output schema exists (as per context signals), the description covers the return format and pagination. It also addresses error handling. For a read-only list tool, all necessary context is provided.

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?

With 0% schema description coverage, the description must compensate. It explains team_id (fallback) and page (0-indexed), and mentions return format which relates to response_format. An example is provided. However, it doesn't explicitly list all parameters in a structured way, but still adds significant value.

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 'List the Workspace's saved task templates.', specifying the verb and resource. It distinguishes from siblings like get_folder_templates and get_list_templates by noting it's for workspace-level templates.

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?

Provides explicit 'When to Use' (discover template ids before creating a task) and 'When NOT to Use' (not for Folder/List templates, directing to other tools). This gives clear guidance and alternatives.

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