clone_task

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

With no annotations, the description must fully disclose behavioral traits, but it only says 'Clone a task'. It does not explain if the source task remains unchanged, what permissions are needed, or what the output looks like. The input schema provides some parameter details, but the description adds no behavioral context.

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 extremely concise (3 words) but is under-specification rather than efficient. It lacks structure or front-loading of key information, and does not earn its place given the tool's complexity.

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?

For a tool with 6 parameters, no output schema, and a nontrivial operation like cloning, the description is inadequate. It does not explain the cloning process, default behaviors, or relationship to other task operations. The context is incomplete for an AI agent to use correctly.

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 input schema has descriptions for 4 out of 6 parameters (67% coverage), including 'fields' and 'status'. The description 'Clone a task' does not add further semantic value beyond the schema. However, the schema itself already clarifies parameter usage, so a baseline of 3 is appropriate.

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 states 'Clone a task', which is a clear verb+noun combination indicating duplication of a task. However, it lacks specificity on what aspects are cloned (e.g., fields, structure) and does not distinguish it from similar tools like 'create_task' or 'clone_board'.

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 usage guidelines are provided. There is no indication of when to use this tool over alternatives such as 'create_task' or 'clone_board'. The description does not specify prerequisites or context for appropriate use.

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