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

With no annotations, the description carries the full burden and does well: it discloses cost ('Free'), no signup, that every response states its source, and the failure semantic that it returns 'unknown' rather than 'does not exist'. It omits rate limits and whether reads hit the live ledger, so it stops short of exhaustive.

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 the core value (risk view and the fields it exposes), followed by cost, the paid alternative, and failure semantics. Dense but nearly every clause earns its place; the pricing detail on the alternative endpoint is the only mildly expendable element.

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, so the description must describe returns — and it does, listing the concrete risk fields and the 'unknown' fallback. It leaves the exact response shape and any rate/access limits unspecified, but for a free read-only risk lookup it is largely complete.

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% and the single parameter's format (48-hex MPTokenIssuanceID) is already documented in the schema. The description repeats the same '48-hex MPTokenIssuanceID, required' fact, adding no meaning beyond the structured field, so the 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 verb+resource ('Get the risk view of one XLS-33 Multi-Purpose Token issuance') and enumerates exactly what it returns: clawback, freeze, require-auth, transferability, and issuer XRPLScore. An agent can distinguish this from search_mpts, verify_mpt_registry, or get_issuer_mpts without opening any schema.

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?

Frames the when ('before touching it') and names an explicit alternative: the paid x402 endpoint at GET /api/x402/usdc/mpt/{id} for the full issuer picture. The routing is clear, though it's presented as a paid upgrade path rather than a when-not-to-use-this condition, and no other sibling is compared.

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