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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description adds nothing beyond that: it doesn't say what the duplicate looks like (name, public/private state, whether it is enabled), nor whether the original is modified. The HTTP path is documentation residue, not behavioral insight.

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?

Very short and front-loaded, which is good, but the second sentence ('POST /api/v2/strategy/reaction/code/duplicate') merely restates the tool name and endpoint convention without adding information, so it fails the 'every sentence earns its place' test.

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 mutation tool with no output schema and an opaque nested body, the description leaves key facts unstated: what is returned, whether the duplicate inherits the original's settings, and any permission requirements. It is too thin for an agent to call confidently.

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?

Only one parameter, and the description says nothing about it. Reported schema description coverage is 0%, so the description should carry the burden of explaining that 'id' is the source reaction's ID, but it does not; the agent must infer this from the field name alone.

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 clear verb ('Duplicate') and resource ('a code reaction'), which is unambiguous on its own. It does not explicitly distinguish itself from the close siblings post_strategy_reaction_llm_duplicate or post_strategy_code_duplicate, so it relies on the tool name for differentiation.

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?

No when-to-use guidance, no prerequisites (e.g., the source reaction must exist or be owned by the caller), and no mention of the sibling duplicate tools for LLM reactions or code strategies. The agent gets only the action, not the context for choosing it.

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