write.asset_manager.cow_swapper

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

Adds context beyond annotations: explains it's an encoder (consistent with readOnlyHint), returns a specific data structure for subsequent use, and is combinable with other intent tools. No contradiction 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?

Five concise sentences, front-loaded with purpose. Could combine sibling distinction with usage note slightly, but no unnecessary words. Well-structured.

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?

Completely describes purpose, use case, dependencies, return format, and integration. Output schema existence reduces burden, but description still covers key details for an encoder tool.

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 has 100% coverage with clear descriptions for both parameters (enabled, chain_id). Description adds no additional semantics beyond schema, meeting baseline expectation.

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?

Clearly states the tool encodes args for standalone CowSwap mode, enabling ERC20 swaps via CoW Protocol with MEV protection. Explicitly distinguishes from sibling tools (compounder_staked, yield_claimer_cowswap).

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 explicit when-to-use guidance by contrasting with coupled automation siblings, notes required additional signature, specifies chain (Base only), and explains output usage with write.account.set_asset_managers.

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