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

Beyond the annotations, it discloses important behavioral context: the call returns terms rather than the answer, the answer is sold over x402, holder-pass authentication requires a signature and no transaction, pricing is stated, and the result is cross-checked against getAccountLiquidity with disagreement surfaced. This is unusually transparent for a paid read-only external tool.

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 key purpose and payment terms are front-loaded, but the description is a long run-on sentence with nested parentheticals and repeated payment/endpoint details. It contains useful information but is not efficiently structured.

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 complex paid external tool with no output schema, it provides strong context on pricing, authentication, external endpoint, and cross-check behavior. The main missing piece is how it relates to the sibling `venus_health_factor` tool.

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 100%, so the single `task` parameter is already documented. The description adds little parameter-specific detail beyond reinforcing that the address should be included in the task, which is already in the schema.

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 clearly states that it computes a Venus health factor and liquidation distance, including collateral drawdown and a stress table. It is specific about the resource and computation, but it never distinguishes itself from the sibling tool `venus_health_factor`.

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?

It explains payment mechanics, but gives no guidance on when to use this tool instead of the sibling `venus_health_factor`. There is no explicit when-to-use, when-not-to-use, or alternative-selection guidance.

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