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

The annotations already establish readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it is non-custodial, moves and holds no funds, and a settlement quote is not execution proof – a meaningful caveat about the limits of the output.

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?

Two tight sentences, no filler, with the core operation stated first and the caveats appended. Every clause carries information an agent would otherwise have to guess.

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 single-parameter tool this is close, but with no output schema the description should sketch what a "quote and plan" returns (rate, route, expiry, fees) so the agent knows whether the result is usable. The authentication and custody caveats are covered, but the response shape is not.

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 carry the weight: it does the important job of naming the parameter's unit as a USDC atomic amount, which the bare string pattern ^[0-9]+$ does not convey. However it stops short of specifying the atomic scale (e.g. 6 decimals) or bounds, so meaningful detail is still missing.

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 opens with a concrete verb pair ("Quote and plan") and a named resource ("OmniDome Settlement Fabric") scoped to a USDC atomic amount, so the agent knows exactly what operation this is. It does not explicitly distinguish itself from the discover_/read_/check_ siblings, but the resource and verb are distinct enough that confusion is unlikely.

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?

Usage is only implied – the agent must infer that this is a pre-settlement pricing step rather than a discovery or join action. There is no explicit "use this when X, use sibling Y instead" routing and no stated prerequisites for calling it.

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