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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered, but the description adds nothing behavioral: it does not say a new reaction is created, whether the copy gets a new ID/name, whether it lands in the same folder, or whether the source is mutated. The REST path echoes the tool name rather than disclosing behavior.

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 short, front-loaded sentences with no wasted wording; the verb and resource come first. The trailing REST path is redundant with the tool name but not harmful.

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?

This is a mutation tool with no output schema, so the description should explain what duplication produces (new reaction ID, copied configuration, placement). It also omits whether folder/status fields on the source are carried over. For a duplicate endpoint, that leaves the agent guessing about the result.

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 reported as 0% and the description mentions no parameters at all. The nested 'id' field does have an inline description in the schema ('Reaction ID to duplicate'), but the description contributes zero meaning beyond it, and the wrapper 'body' object is undocumented in both places.

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 ('Duplicate') and resource ('LLM reaction'), which separates it from the create tool post_strategy_reaction_llm and the code analogue post_strategy_reaction_code_duplicate. It does not explicitly name siblings, but the resource noun is distinctive enough for an agent to route correctly.

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?

There is no guidance on when to duplicate versus creating a new reaction (post_strategy_reaction_llm) or editing one (put_strategy_reaction_llm_id). The usage is only implied by the word 'Duplicate', and no prerequisites or exclusions are stated.

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