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

Annotations only declare non-read-only, non-destructive, non-idempotent, non-open-world; the description adds the substantive behavior: a NEW draft is created rather than the source modified, applications are deliberately excluded, and stage emails are carried over. That is real context beyond the annotations and consistent with idempotentHint=false.

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?

One sentence, front-loaded with the action and scope, with the return value appended. Every clause (details, form, stages, emails, without applications) carries distinct information and nothing is repeated.

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 one-parameter mutation with full schema coverage, the description covers what is copied, what is omitted, that the result is a draft, and the shape of the return value (new job's ID) despite there being no output schema. Nothing needed to invoke it correctly is missing.

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?

Single parameter at 100% schema coverage, and the schema already explains it is the job's ID sourced from list_jobs. The description adds no format, sourcing, or constraint detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource (copies a job) and enumerates exactly what is carried over (details, form, stages with emails) and what is not (applications). This makes it naturally distinguishable from create_job and get_job, though it never names those siblings explicitly.

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 copy semantics imply the use case (cloning an existing job rather than building one from scratch), but there is no explicit 'use this instead of create_job when...' statement and no prerequisites or exclusions stated. Usage is inferable but not guided.

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