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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds that the quote returns fee and speed for both a fast and a standard option, which is genuinely useful, but says nothing about amount units, limits, or quote validity/expiry.

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 sentences, both load-bearing, with the capability stated before the usage restriction. No redundant restatement of the title.

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 two-parameter read-only quote tool with no output schema, the description covers what is computed (fee and speed, two tiers) and the domain restriction. Minor gaps remain around amount formatting and whether the returned quote is time-bound.

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 coverage is 0%, so the description must compensate. It does partially: it establishes that the amount is denominated in USDC and that the network is the destination chain. It stops short of format guidance (e.g. amount as string decimal, maxLength 40) or whether the network must come from get_stablecoin_networks.

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?

Specific verb+resource: estimates fee and speed for sending USDC from Poplin to another network, and names the fast and standard tiers. It implicitly separates itself from get_send_quote by scoping to stablecoin-to-another-network, but never names that sibling explicitly.

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?

'Use it only when someone asks about sending stablecoins to another network' is an explicit when-to-use clause with a clear exclusion. It does not, however, point at the alternative to use for fiat sends or network listings.

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