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

With no annotations provided, the description carries the full burden. It discloses the return content (fee, treasury wallet, escalation rules, submission endpoint), plus details about improvement hints and the POST /api/progress and /api/bundle options. It's honest about what data users get — actionable hints per session and trajectory reports — which exceeds the minimum disclosure bar.

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 front-loaded with the core content (fees, wallet, escalation, submission endpoint) but then extends into promotional detail about improvement hints, POST /api/progress, and fleets/bundles. These additional details are informative but somewhat structured more like marketing copy than a tight API description, and the long continuous sentence reduces scannability.

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 0-parameter informational/manifest tool with no output schema, the description is quite complete. It covers the main content, secondary offerings (progress reports, bundles), and related endpoints. The only gap is that it doesn't explicitly state the return format or whether the pricing is retrieved from a live source, but for a manifest document tool this is adequately comprehensive.

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 tool has 0 parameters, so the description receives a baseline of 4 per the rubric. There's nothing additional to clarify since the schema already fully covers an empty parameter set (100% coverage trivially). The description correctly focuses on output content rather than parameter semantics.

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?

Clearly identifies itself as the current pricing manifest covering fees in Solana lamports, treasury wallet, failure-escalation rules, and benchmark submission. It distinguishes itself from siblings like preview_fee (which presumably predicts a fee) by positioning get_pricing as the authoritative manifest document. The verb is implicit ('retrieves/describes') but the resource scope is explicit and specific.

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 communicates substantial context about what the manifest contains, but does not explicitly state WHEN to use this tool versus alternatives like preview_fee or get_network_stats. It implies usage as a reference/manifest lookup, which is reasonable for a 0-param informational tool, but there's no explicit when/when-not guidance.

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