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

With annotations already marking this as non-read-only and non-destructive, the description adds useful behavioral context: the action is free, records attribution, incurs a 15% clone-creator fee share, and returns a deployable template rather than performing deployment itself. These are beyond the schema but consistent with annotations.

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 compact sentences front-load the action and then add only high-value workflow and cost details. Every clause earns its place; no redundant filler.

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 mutate-style tool with an existing output schema and annotations, the description covers the core behavior, cost, attribution, and the follow-up action (strategy create tools). It is slightly incomplete only in parameter-level detail and explicit sibling differentiation.

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?

The opening sentence maps template_id to the published strategy config and wallet_address to the destination wallet, which covers the required parameters. However, the description does not explain caller_id at all, and with 0% schema coverage the agent must infer type/format for the core parameters.

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?

Sentence one states a specific verb+object: 'Clone a published strategy config to a wallet' and adds the attribution nuance. It distinguishes the tool's role from the sibling strategy create tools by noting the returned config_template is meant for subsequent deployment.

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 description frames the intended workflow: clone a published config, receive a config_template, then deploy via strategy create tools. This clearly signals when to use the tool, though it does not explicitly enumerate alternatives or exclusion conditions.

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