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

Annotations already declare idempotent, open-world, non-destructive behavior. The description adds important non-schema context: the tool is a paid x402 endpoint costing 0.01 USDC and expects an X-Bazaar-Key, which an agent needs before invoking it.

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 a single compact sentence plus a paid-access prefix. Every element earns its place, and the core calculation purpose is stated immediately after the payment note.

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 low-complexity calculator with no output schema, the description gives enough information to understand the computation and paid access requirement. It could be more complete by specifying the return format, but the core behavior is adequately covered.

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 schema fully documents collateral_usd, but the description adds meaningful semantic information by naming debt and liquidation threshold as required inputs even though they are not explicit schema properties. It does not, however, explain expected formats or units for those additional inputs.

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 verb (Calculate) and specific resources (Aave/Compound lending health factor and collateral drawdown safety buffer), with the inputs it uses. This is specific enough to distinguish it from adjacent DeFi calculators and risk suites in the sibling list.

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 description implies the tool is used when computing a lending health factor from collateral, debt, and liquidation threshold. However, it does not say when to prefer it over adjacent tools such as risk_bundle or suite_defi_execution_risk, nor does it state exclusions or prerequisites.

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