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

Annotations already establish that this is a non-destructive, open-world read. The description adds useful behavioral context beyond annotations by identifying the source as each market contract, specifying best-first ordering, and noting that the free rates are not cross-checked against the market rate model.

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 substantive information is front-loaded, but the phrasing is somewhat promotional and indirect, with phrases like 'the free half' and 'the paid half' adding word count. It remains understandable, but a more direct statement of scope and ordering would be cleaner.

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 zero-parameter read tool with no output schema, the description gives enough context to know that it returns all Venus market supply rates on BNB Chain, sorted best first, with venus_usdt_rate_pct highlighted. It does not fully describe the return structure, but the core result is clear.

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?

The tool has no input parameters, so parameter semantics are minimal by design. The baseline for a zero-parameter schema is 4, and there are no parameter meanings that the description needs to compensate for.

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 a specific resource and scope: the supply rate of every Venus market on BNB Chain, read from each market contract and ordered best first. It distinguishes this free rate snapshot from the paid analysis, though it does not explicitly name the sibling tool yield_plan.

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?

Usage is implied through the free-versus-paid framing: this tool provides raw rates, while the paid half evaluates whether moving a deposit pays for itself. However, it does not explicitly say when to choose this over yield_plan or state exclusions and prerequisites.

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