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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered; the description adds real value by disclosing the 180-second expiry and that `expiresAt` is unix ms. It does not describe auth requirements, rate limits, or what happens if a stale quote is passed downstream, so it enriches but does not fully characterize behavior.

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?

Four short sentences, front-loaded with the purpose and mode semantics, then chaining guidance, then expiry and unit conventions. Every sentence carries distinct information with no restatement of the title.

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?

With no output schema, the description usefully covers the return envelope, the `rewards` field, and expiry semantics, and it explains the conditional slippage parameter. Missing only edge conditions such as expired-quote failure behavior or supported chains.

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 80%, and the description goes beyond the bare enum by explaining what each `mode` value does and that 'compound' requires slippage. It also flags that amounts are base-unit integer strings, though it does not restate the slippage decimal-vs-fixed-point convention.

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 and resource: 'Quote claiming rewards', and names the downstream consumer (build_claim), which separates it from the build_* siblings. It never explicitly says it does not submit a transaction, so the quote-vs-execute boundary is implied by naming convention rather than stated.

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?

Gives concrete when-to guidance through the two modes ('send' pays the owner, 'compound' swaps into the position and requires slippage) and explains that the returned `rewards` feed build_claim. There is no explicit exclusion such as 'do not use to execute; use build_claim' or a note on which chains/positions are supported.

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