list_pricing

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

No annotations are supplied, so the description carries the full load. It discloses two behaviorally important facts: the call is free (contrasting with the USDC-priced siblings) and it reports whether a signer is configured, implying this call itself needs no signing. It doesn't state rate limits, response size, or what happens without a signer, so it is 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?

Three short sentences, front-loaded with cost and scope, then the ordering instruction. The one-word "Free." opener earns its place because cost is the primary differentiator against paid siblings.

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 no-argument discovery endpoint with no output schema, the description compensates by enumerating the returned fields (USDC prices, PayTo, network, params, signer status). That is exactly the information an agent needs before deciding which sibling to call next.

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 takes no parameters, so there is nothing for the description to disambiguate; baseline is 4. The listed field names in the description describe the response, not inputs, and do not conflict with the empty schema.

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?

"List all Solana Alpha API tools" names a specific verb and resource, and the enumerated contents (USDC prices, PayTo, network, params, signer status) tell the agent exactly what the listing contains. This clearly separates it from the siblings (get_price, get_news, etc.), which each fetch one data type.

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?

"Call this first" gives an explicit ordering directive that is the main usage decision for a catalog tool. It stops short of naming when-not-to-use conditions or explicitly pointing at siblings as alternatives, but for a zero-parameter discovery endpoint the guidance is operationally sufficient.

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