clickup_create_task_from_template

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

Annotations indicate non-read-only, non-destructive, non-idempotent. Description adds that it performs a POST request and returns a confirmation string with new task name and ID. Also mentions error handling (404). No contradictions. Small gap: no explicit mention of side effects beyond creation.

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 well-organized with clear sections: overview, endpoint, usage guidelines, returns, example, error handling. No redundant sentences; every line serves a purpose.

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 input schema describes parameters and an output schema likely returns the result, the description provides all necessary additional context: purpose, HTTP method, how to get template IDs, when to use, example, and error handling. Covers all key aspects for correct tool selection and invocation.

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?

Input schema already describes each parameter (name, list_id, template_id). Description adds context by showing the endpoint pattern and explaining how to obtain template IDs via `clickup_get_task_templates`. Provides a concrete example. Schema coverage is 0% but parameters are described in the schema, so description adds complementary 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?

Clearly states 'Create a task in a List from a saved task template.' Specifies verb, resource, and distinguishes from sibling `clickup_create_task` (plain task). Mentions the HTTP POST endpoint for technical clarity.

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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, with direct reference to alternative tool `clickup_create_task` for plain tasks. Offers actionable guidance on when this tool is appropriate.

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