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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely new behavioral context — that the intent is signed, that routing is atomic across chains, and the typical 30-60 second settlement window. It does not cover auth/permission needs or what happens on a failed settlement.

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 tight sentences: what it does, the prerequisite, and the follow-up. The prerequisite is front-loaded before the polling hint, and there is no filler.

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 mutation tool with no output schema and full schema coverage, the description supplies what an agent needs to sequence correctly: prerequisite quote, cross-chain atomicity, and settlement timing plus the tracking tool. It leaves out failure/refund behavior and permission requirements, which keeps it from being fully 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%, so the schema already explains quoteId, recipient, and workflowId. The description only restates the quoteId provenance ('Call near_quote first'), adding no syntax, format, or constraint 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 verb and resource ('Submit a cross-chain payment intent to the NEAR 1Click solver network') and adds the mechanism ('creates a signed intent that routes the payment atomically'). This clearly separates it from sibling near_quote (which produces the quote) and near_intent_status (which tracks it).

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 an explicit prerequisite ('Call near_quote first to obtain a quoteId') and an explicit follow-up ('poll near_intent_status to track progress'), which is strong routing guidance. It does not state when not to use the tool or what happens if the quote expires, so it stops short of a 5.

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