Estimate Solana Priority Fees

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds transparency about cost ($0.002). It does not mention other behavioral aspects like rate limits or data freshness, but the annotations cover safety and idempotency.

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?

The description is extremely concise with two sentences, front-loading the core purpose. Every word adds value, and there is no unnecessary information.

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?

The tool is simple with one optional parameter and no output schema. The description covers the purpose, scope, and cost, but does not describe the output structure (e.g., which quantiles are returned). This minor gap prevents a perfect score.

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%, but the description clarifies the sole parameter 'accounts' by implying that providing account addresses yields localized quantiles while omitting it yields network-wide ones. This adds meaning beyond the schema, though it does not detail account format or behavior of empty array.

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 clearly states the tool returns 'priority-fee quantiles' for either network-wide or account-localized scope, with the specific verb 'Return' and resource 'priority-fee quantiles'. It distinguishes itself from unrelated siblings, and the context 'before choosing a compute-unit price' clarifies its purpose.

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?

The description implicitly indicates when to use ('before choosing a compute-unit price') and mentions cost ($0.002). However, it does not explicitly exclude scenarios or mention alternative tools, though siblings are unrelated, making this less critical.

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