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

There are no annotations, so the description carries the burden. It discloses the free nature, the 404 behavior for out-of-scope cards, the pointer to the paid quote, the 'Informational only — not financial advice' caveat, and the transparency artifacts like merkle proof links. It does not explicitly declare read-only/no side effects or mention auth/rate limits, but the read-only intent is strongly implied.

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 dense but well organized: coverage and derivation steps first, then failure behavior and paid alternative, then usage trigger and related URLs. A few phrases repeat the free/board concept, but every sentence adds relevant decision-making or invocation context.

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?

There is no output schema, so the description must convey return content, and it does: six derivation steps, price source, merkle proof links, and 404 behavior. It also provides the rated universe endpoint and a human page, giving an agent enough context to call the tool and recover when a card is outside the free board.

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 0%, so the description must compensate. It explicitly enumerates term_days as 7, 14 or 30, which is valuable. However, product_id is only implied to be the trading-card identifier on the free board; its format, source, or lookup is not directly explained, leaving a partial semantic gap.

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, concrete behavior: a free worked derivation of safe lending terms for a trading card on the free board, including the exact derivation pipeline. It also clearly distinguishes itself from the paid /api/v1/loan-terms quote, so an agent knows this is the preview, not the full paid quote.

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 explicitly says 'Use this when: an agent wants collateral math for a card, or to explain how the Loan-Terms Oracle derives an LTV before paying for a full quote.' It also states the exclusion boundary clearly: cards off the free board return 404 and point to the paid quote endpoint.

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