hyre-yields

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

With no annotations, the description alone should disclose behavioral traits. It states the tool returns top yield pools sorted by APY, but does not mention whether it's a read-only operation, how data freshness is handled, whether pagination or rate limits apply, or what the '$0.002' refers to (cost?). This leaves significant behavioral ambiguity.

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 very brief and front-loaded with the core function ('Top yield pools multi-chain sorted by APY'). However, the trailing '$0.002' is unexplained and likely a typo or misplaced cost indicator, which detracts from clarity and wastes one of only eight words.

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?

No output schema and no annotations place a heavy burden on the description. It fails to explain the return payload shape, whether the list supports pagination, what 'multi-chain' means in terms of default chains, or the meaning of '$0.002'. For a tool with four parameters and no other documentation, this description is insufficient.

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%, providing basic meaning for each parameter (chain filter, max results, min APY, stablecoin filter). The description adds that results are multi-chain and sorted by APY, but does not elaborate on parameter interactions or value formats beyond what the schema already states.

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 states it lists 'Top yield pools multi-chain sorted by APY', which clearly identifies the tool's function (listing yield pools) and the sort order (by APY). This differentiates it from siblings like hyre-pools or hyre-tvl, though it doesn't explicitly name them. The trailing '$0.002' is ambiguous but doesn't obscure the primary purpose.

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 phrase 'Top yield pools multi-chain' implies usage for discovering high-yield opportunities across chains. However, it provides no explicit guidance on when to prefer this tool over siblings like hyre-pools or hyre-tvl, nor any 'when not to use' exclusions.

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