copy_template

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a mutation-like operation (copying creates a new template) but does not mention side effects, whether the source is modified, required permissions, or what happens after copying (e.g., returns the new ID). This is a significant gap for a copy operation.

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 only one short sentence, but it is under-specified rather than efficiently concise. It lacks essential details and does not front-load parameters or outcomes. It is not a well-structured description for 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 copy operation with a required sourceTemplateId and an optional newName, and with no output schema, the description is severely incomplete. It does not explain the return value, the effect of the copy, or any constraints. An agent would not know how to call this 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?

Schema description coverage is 0%, so the description must compensate. It does not mention sourceTemplateId or newName at all. The agent has no understanding of what these parameters represent or how they affect the copy operation.

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 a clear verb ('copy') and resource ('template'), and adds that it selects the new template. This distinguishes it from create_template (which likely creates from scratch) and delete_template, though it doesn't explicitly name alternatives. It is specific enough to understand the core function.

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 is provided on when to use this tool versus the many siblings (create_template, select_template, etc.). There is no mention of context, alternatives, or prerequisites. The agent is left to infer usage from the name and description.

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