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

With no annotations, the description carries the full behavioral burden. It usefully discloses pricing ($0.02 per call), which is real value add, but says nothing about return shape, whether both gainers and losers are always returned, or rate/usage limits.

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?

Three short clauses, front-loaded with the core behavior, then the framing (anomaly feed), then the cost. Nothing is wasted, though it is terse enough that it under-explains rather than over-explains.

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 4-param tool with no annotations, no output schema, and zero required parameters, the definition leaves several things unsaid: what the response contains, how chain interacts with results, and when to prefer this over defi_top_yields. It is usable but not complete.

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 50%: limit and minTvl carry their own defaults in the schema, while chain and window do not. The description mentions the 1d/7d window values and the up/down split, partially covering the undocumented params, but says nothing about chain filtering or how limit splits across sides.

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 resource (pools) and the exact metric (largest APY change, up and down) with the two supported windows, which is enough to distinguish it from a static ranking tool like defi_top_yields. It stops short of naming siblings explicitly, so an agent must infer the delta-vs-level distinction itself.

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?

"Anomaly feed" gestures at a use case but gives no explicit when-to-use guidance, no contrast with defi_top_yields or stablecoin_peg_monitor, and no prerequisites. The agent is left to guess whether this is for monitoring, research, or alerting.

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