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

Annotations already declare non-read-only, non-idempotent, non-open-world behavior. The description adds permission context ('requires automation_rules:write') and return behavior ('Returns rules_copied'), which goes beyond annotations. However, it omits what gets copied by default, whether overriding the source or side effects on the original pipeline.

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?

Two tight sentences with the core action front-loaded and the copy_rules caveat immediately after. No filler, though one more sentence could have covered required parameter semantics without bloat.

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 6-param mutation tool with 0% schema coverage and no output schema, the description covers the action, one optional flag, a permission prerequisite, and one return field. It leaves important gaps: what the clone defaults inherit, semantics of pipeline_id/name/slug, and idempotency key behavior.

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%, so the description must compensate. It clarifies copy_rules' effect and the automation_rules:write requirement but says nothing about required pipeline_id/name/slug semantics, request_id, or idempotency_key, leaving four of six parameters undocumented.

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 ('Clone') plus the resource ('a pipeline and its stages') and an optional extension ('copy its workflow rules too'). Distinguishable from yardstick_pipelines_create and yardstick_pipelines_update since cloning is an explicit duplicate operation.

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 conditional 'Set copy_rules to copy its workflow rules too' implies when to enable rule copying, which is useful context but not an explicit when-to-use vs alternative. It does not say when to choose clone over creating a new pipeline or when not to use it.

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