ponzu_farm_claim_eth

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

No annotations provided, so description carries full burden. Discloses repeatability and a constraint, but lacks details on error behavior, permission requirements, or state changes.

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 concise sentences with no wasted words. Information is front-loaded with purpose and usage guidance.

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 simple two-parameter claim tool, description covers purpose, when to call, and a critical limitation. Lacks details about failure modes or gas implications, but sufficient for selection and invocation.

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 100%, with parameters already described as 'LiquidityCard NFT ID' and 'Farm contract address'. Description adds no additional meaning beyond what schema provides.

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?

Description uses specific verb 'claim', resource 'WETH rewards', and context 'Ponzu farm'. Distinguishes from siblings like 'ponzu_claim_eth' and 'ponzu_farm_claim' by specifying WETH rewards and the constraint 'Cannot claim after primary token claim'.

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?

Explicitly states 'Repeatable — call as rewards accumulates' (when to use) and 'Cannot claim after primary token claim' (when not to use). No direct alternatives mentioned, but sibling tools provide context.

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