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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive operation. The description adds genuinely useful behavior beyond that: unmatched rules are left off and existing rules are preserved. It omits auth/permission needs, whether the operation can partially fail, and the meaning of idempotency_key given 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?

A single compact sentence with the copy action and the key preservation guarantee front-loaded. There is no padding, though brevity here edges toward under-specification rather than efficiency.

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 six-parameter mutation tool with nested objects, no output schema, and zero schema descriptions, the description is too thin. An agent cannot determine from it how matches map rules, what source_digest validates, or what a successful apply returns, so it is not complete enough to call 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% across six parameters, including nested matches and a hex-patterned source_digest. The description only vaguely gestures at 'chosen matches' and never explains request_id, source_digest, idempotency_key, or how the source type enum (starter vs job) is used, so it fails to compensate for the coverage gap.

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 specific verb (Copy) and resource (reviewed rules into a job), which is more informative than the bare tool name. However, it does not distinguish this tool from close siblings like yardstick_automation_rules_copy or yardstick_automation_starters_save_job, leaving the agent to infer which copy path applies.

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?

It hints at the mechanism ('using chosen matches') but gives no explicit when-to-use, when-not-to-use, or alternative tools. With several overlapping copy/save starter siblings present, the lack of routing guidance is a real gap.

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