get_pricing

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

With no annotations, the description carries the burden. It states 'Live' and 'No per-request fees' which suggests a read-only informational retrieval, but it does not explicitly mention side effects, data freshness, or security constraints. This is adequate but not exhaustive.

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 succinct, using one sentence to convey the core content and a second short sentence to clarify what it does not include (per-request fees, compute units). Every word adds value; no fluff or redundant phrasing.

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?

Given the absence of parameters and output schema, the description provides sufficient context. It clearly outlines the type of information returned (plans, rate limits, features) and the pricing model (flat-rate, no per-request fees), which fully equips an agent to decide when to invoke this tool.

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?

There are zero parameters in the schema, and the description does not mention any. The baseline for 0 parameters is 4, and no additional parameter explanation is needed. The description effectively communicates that no input is required.

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 states the tool provides live flat-rate pricing for SwiftNodes RPC, enumerating specific content (monthly plans, HTTP/WS rate limits, included features). The name 'get_pricing' and sibling tools (list_chains, get_chain, etc.) make it obvious this is the tool for pricing information, distinct from chain or method details.

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 implies usage when pricing information is needed, and the sibling tools' purposes (chains, methods, endpoint probing) contrast naturally. However, it does not explicitly state 'use this when you need pricing' or provide conditional guidance, so it falls short of a perfect score.

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