copy_job

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

With no annotations, the description carries full burden but merely states the action. It does not disclose side effects, permission requirements, or whether the operation is reversible. 'Duplicate' implies creation of a new job, but details on what exactly is copied are missing.

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 a single sentence of 4 words, highly concise. It front-loads the action clearly. However, it could be more informative without losing brevity.

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?

Despite having an output schema, the description does not explain what the tool returns or how the duplication works in detail. It lacks context on whether it copies the entire job definition, schedules, or dependencies. For a simple operation, more behavioral context is expected.

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 only parameter, job_id, is not described in the description. Schema description coverage is 0%, so no additional meaning is provided beyond the parameter name. While the name is slightly self-explanatory, the description should clarify its role (e.g., 'the ID of the job to duplicate').

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?

Description states 'Duplicate an existing job.' with a specific verb and resource. It clearly distinguishes from sibling tools like execute_job, stop_job, etc., which perform different actions on jobs.

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 alternatives. There is no mention of prerequisites, typical use cases, or scenarios where other tools might be more appropriate.

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