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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: cost ($0.01 USDC on Base, eip155:8453), the payment mechanism (x402 in params._meta), and the transport (HTTP GET). It says nothing about data freshness/caching, rate limits, or failure modes, which matter for a 'current' estimate.

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 dense fragments with the purpose front-loaded, followed by price and transport. Nothing is padded. The raw HTTP endpoint is marginal for an MCP caller but is short and useful for debugging.

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 zero-parameter, no-annotation, no-output-schema read tool, this covers the essentials: what it returns (a priority fee), in what unit, at what price, and how payment is supplied. The remaining gap — data freshness — is minor at this complexity.

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?

The schema declares zero properties, so the baseline is 4, but the description actually earns it by revealing a required out-of-schema input: params._meta["x402/payment"]. That is information an agent could not get from the schema. It stops short of describing the payment payload's structure, so not a 5.

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 — 'Current Solana priority fee estimate' — and even specifies the unit (micro-lamports per CU). It is clearly distinct from sibling solcheck tools like balance, slot, token, and tx, though it never explicitly names a sibling to contrast with.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named (e.g. whether solcheck__tx already returns a fee). Usage is only implied by the resource name. The one precondition it does convey is that a paid x402 call is required.

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