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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real value beyond that: it specifies exactly what is destroyed (the entire routing tree), that rotation settings are adopted, and that later scheme edits do not propagate to the applied copy — a non-obvious snapshot behavior. It stops short of saying whether the replacement is recoverable or what the response contains.

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?

Three short clauses, front-loaded with the destructive effect before the snapshot caveat and the lookup hint. Every sentence carries information an agent needs to call the tool correctly; nothing is padded.

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 with annotations covering the safety profile and no output schema, the description supplies the operation's net effect, its non-obvious snapshot semantics, and how to source the undocumented id. Only failure behavior and result payload remain unstated, which are minor here.

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 only 50%: campaign 'id' is documented in the schema while 'flow_scheme_id' has no description there. The description partially compensates by telling the agent where the scheme id comes from (list_flow_schemes) and by naming the target resource, but it adds no further constraint or format detail for either parameter.

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+resource (apply a flow scheme to a campaign) and immediately defines the operation's effect: the campaign's routing tree is replaced by a copy of the scheme's flows plus its rotation settings. This clearly separates it from create_flow_scheme/update_flow_scheme, which manipulate the scheme itself rather than a campaign's routing.

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?

Provides a concrete discovery pointer (use list_flow_schemes to obtain the scheme id) and an implicit usage condition via the snapshot semantics. It does not, however, state when an agent should copy a scheme versus building routing directly via campaign updates, nor any preconditions such as campaign state.

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