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

With no annotations, the description carries the full behavioral burden and does so: paid x402 call at $0.02 USDC on Base against GET /api/lending/grade, it returns a payment resource rather than a result, and it is not yet live so it returns available:false with no charge. It also enumerates the inputs feeding the grade (size, utilization, first-loss cover ratio, late/impaired/defaulted loans, unrealized loss, realized yield).

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?

Front-loaded with purpose and scope, then layered caveats (paid call, returns payment resource, not live yet, params). Dense but each clause is load-bearing; the final params sentence is the only mildly redundant part given the schema.

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 exists, and the description compensates by specifying what a call produces (a payment resource), the concrete not-live response shape (available:false, 503, no charge), and the grading inputs. An agent has everything needed to decide and invoke correctly.

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%, so both parameters are already fully documented, including the 64-hex pattern and the 'detected when omitted' note for type. The description merely restates id as required and type as optional, adding no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific resource and output (A-F risk grade for one XRP Ledger lending vault or loan broker) and the exact input domain (64-hex Vault or LoanBroker ID). It also explicitly distinguishes itself from an adjacent concept ('Not a credit rating') and from what it is not (a computation tool).

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?

Explicitly tells the agent when this applies (grading a single vault or broker from on-ledger data), what it actually does on invocation (returns the payment resource, does not compute the grade), and the failure mode to expect (available:false / 503 upstream, no charge) because the protocol is not live. No sibling tool could be mistaken for it, so no alternative-routing sentence is needed.

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