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

The annotations are essentially defaults (readOnlyHint=false, destructiveHint=false), so they carry little; the description usefully adds the solver-network dependency and the near_status prerequisite. However, it says nothing about whether the quote is binding, how long it is valid, whether calling it has side effects on the destination chains, or what the response contains. Note: readOnlyHint=false is mildly at odds with the retrieval framing ("Get a quote"), but since false is the non-asserting default it is not a genuine contradiction.

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?

Three short sentences, front-loaded with the resource and provider, then use case, then prerequisite. No filler or repetition. It could arguably be even tighter, but every sentence contributes.

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?

Covers what the tool is, what it is for (funding PCC escrow contracts), and the prerequisite call. With no output schema, it would help to state what a quote returns (route, fee, expected amount), and it omits what to do with the quote afterwards (near_intent). For a single-purpose retrieval tool the core context is otherwise present.

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% (amount denomination, chain/asset symbols, optional recipient are all documented in the schema), so the baseline is 3. The description adds conceptual scope ("any source asset on any supported chain") but no syntax, constraint, or default information beyond the schema.

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?

Names a specific verb and resource ("Get a cross-chain payment quote") and identifies the provider (NEAR 1Click solver network / chaindefuser.com), so the agent knows exactly what it produces. It does not explicitly differentiate itself from the nearest siblings near_intent / near_intent_status, which an agent must infer (quote vs. execute vs. poll).

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?

Gives a concrete precondition: "Call near_status first to confirm available chains/assets." That is clear sequencing guidance for a multi-step cross-chain flow. It stops short of naming the execution alternative (near_intent) or stating when not to use a quote, so it is context without exclusions rather than full routing guidance.

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