aap_copy_job_template

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description does not contradict them. The description adds that the operation returns a new template id and name, but it does not disclose side effects such as whether associated permissions or credentials are copied. It provides basic transparency but not deep behavioral detail.

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 concise and structured with an Args/Returns format, making it easy to scan. It uses minimal sentences without unnecessary filler, though the formatting could be slightly tighter.

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 simple two-parameter copy operation, the description covers what the tool does, the parameters, and the return value. It is sufficiently complete for its complexity, though it could mention whether all source template settings are preserved or if any fields are excluded from the copy.

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 schema description coverage reported as 0%, the description compensates by listing both parameters and their meanings: 'template_id (int): Source template ID' and 'name (str): Name for the copy'. This provides functional semantics beyond the raw schema, though it lacks examples or edge-case details.

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 action: 'Copy an existing job template with a new name.' This is a specific verb ('Copy') and resource ('job template') with a clear outcome. It is easily distinguished from sibling tools like create, update, delete, or launch.

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 the usage scenario (duplicating a template with a new name) but does not explicitly contrast it with alternatives like aap_create_job_template. It gives a clear context for use but omits explicit when-to-use/not-to-use guidance or exclusions.

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