write.asset_manager.compounder_staked

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

The description states 'Sets metadata on BOTH the CowSwapper and the Compounder in a single call,' implying a write operation, but the annotation declares readOnlyHint=true. This contradiction misleads the agent about the tool's side effects.

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?

The description is a single dense paragraph that efficiently conveys key information without fluff. It front-loads the core purpose and quickly details the flow. Could be slightly more structured (e.g., bullet points), but remains concise.

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?

Given the tool's complexity (compound + CowSwap for staked positions), the description covers purpose, behavior, parameter guidance, output structure, chain restriction, and composability. With output schema present, the agent has sufficient context to invoke the tool correctly.

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 100%, so baseline is 3. The description adds value beyond schema by explaining sell_tokens as reward token addresses with example (AERO), buy_token as major tokens, and giving context for dex_protocol and chain_id. This helps the agent choose appropriate values.

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?

The description clearly states the tool encodes args for a compounder with CowSwap for staked LP positions, specifying the flow: claim staking rewards, swap to target token, compound back. It distinguishes from siblings like compounder and cow_swapper by explicitly targeting staked positions.

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 explains when to use this tool (for staked LP positions earning staking rewards), provides parameter semantics (sell_tokens as reward tokens, buy_token as major token), and notes chain restriction (Base only) and composability. It does not explicitly exclude non-staked scenarios or mention alternatives, but the sibling list implies them.

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