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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the copy is independent, mirrors the working copy's bottles, and is auto-named '<name> copy' unless a name is supplied. It does not say what happens to later edits or where the copy lives, but this is solid added value.

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 use trigger, with no filler. It is slightly dense with nested qualifiers (working copy, bottles, naming fallback), but every clause carries information.

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 two-parameter mutation tool with annotations present and no output schema, the description covers the trigger, the copy semantics, and the naming default. It leaves unstated whether the copy is a saved or draft artifact and what identifier comes back, but no output schema exists to carry that, so this is a minor residual gap.

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 coverage is 50%: 'formula' is documented (id or exact name) but 'name' is bare. The description compensates for the undocumented parameter by specifying the default naming convention ('<name> copy' unless named), which is exactly the missing semantic an agent needs.

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 ('duplicate a formula') and qualifies exactly what kind of duplicate it produces: an independent copy of the working copy with the same bottles. This distinguishes it from create_formula, branch_version, and save_version without the agent needing to open schemas.

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?

'Use this when the user wants a copy of a formula to try changes on' gives a clear triggering intent. It does not name siblings like branch_version or create_formula as alternatives, so routing remains partly inferential, but the use context is unambiguous.

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