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

Annotations already establish that this is a mutation (readOnlyHint=false) that is not idempotent and not destructive. The description adds substantial non-obvious behavior: matching is by step name/kind and position for steps, by name or mapped status for stages; unmatched copies start disabled and need manual step/stage selection; copies become independent user rules. That is real context beyond the structured hints, though return/idempotency behavior is still unstated.

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?

Three dense sentences, front-loaded with the core action and destination, then matching rules and the unmatched-copy consequence. Every sentence carries information, though the 'Pick a step' / 'Pick a stage' UI phrasing is somewhat opaque without that context.

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?

No output schema exists, so return values need not be described, and the mutation's safety profile is covered by annotations. However, for a copy tool exposing request_id and idempotency_key while declaring idempotentHint=false, the description leaves deduplication/retry semantics and any permission requirements unexplained.

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% across 5 parameters, so the description must carry the full burden. It meaningfully explains job_ids, pipeline_ids and rule_id, but leaves request_id and idempotency_key completely undefined, and gives no format or constraint detail (e.g. the 50-item cap) for the arrays.

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 (Copy) and resource (rule), and even splits purpose into two modes: a hiring-process rule copied to job_ids, or a pipeline rule copied to pipeline_ids. This clearly differentiates it from the automation_rules_create/update/delete siblings, though it never names an alternative 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 two copy modes imply when the tool applies, but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives like automation_rules_create or automation_rules_preview. Usage must be inferred from the two described scenarios.

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