sol_priority_fee

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

Annotations already indicate `readOnlyHint: true` and `destructiveHint: false`, so the description adds value by specifying the return content (percentiles, tiers) and the live-oracle nature. No 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?

One sentence with no wasted words. Front-loaded with the tool's purpose and key details (oracle, output types, usage directive).

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 tool with no parameters and no output schema, the description fully covers what the tool does, what it returns (percentiles and tiers), and when to call it. No gaps.

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 input schema has zero parameters, so no parameter documentation is needed. Baseline 4 is appropriate as the description adds no parameter info but also doesn't need to.

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 uses a specific verb ('Live Solana priority-fee oracle') and clearly states it provides 'current microLamports/CU percentiles and recommended low/medium/high/turbo tiers'. This distinguishes it from sibling tools like `sol_swap` which are for trading, making its purpose unmistakable.

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 explicitly states 'Call before sending any Solana transaction', giving clear guidance on when to use. However, it does not mention when not to use or list alternatives, though the sibling set (e.g., `sol_swap`, `sol_swap_quote`) implies other tools handle transaction execution.

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