get_pricing

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

No annotations exist, so the description carries the full burden. It discloses that the tool returns data, but does not mention any behavioral traits (e.g., cost, rate limits, or idempotency). For a simple getter, the lack of negative side effects is implied but not stated.

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 a single sentence of 8 words, containing only essential information. No redundancy or fluff.

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 description defines the tool's purpose minimally. Without an output schema, the agent does not know the structure of the returned pricing entry point. Given the simple nature (0 params), it is adequate but could clarify what 'canonical pricing entry point' means.

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 no parameters, so schema coverage is 100% and the description adds no parameter-level detail. The baseline for 0 parameters is 4, and the description does not contradict or add confusion.

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 ('Return') and identifies the resource ('canonical pricing entry point for Riftrunner AI'). It clearly distinguishes from sibling tools like list_models and get_official_links, which cover different domains.

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, but does not provide explicit when-to-use or when-not-to-use guidance. However, given the tool's simplicity and lack of alternatives for pricing, it is clear enough.

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