check_pricing

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description indicates a read-only operation, which is appropriate. However, it omits any mention of potential issues like rate limits, authentication requirements, or what happens when invalid model/action combinations are provided. The description is adequate but lacks detail.

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, concise sentence with no wasted words. It is front-loaded and directly states the tool's function. While very brief, it covers the essential information without unnecessary elaboration.

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?

Despite high schema coverage and no output schema, the description does not explain the nature of the pricing information returned (e.g., whether it includes rates, tiers, or just a simple number). For a pricing lookup tool, the agent would benefit from knowing the structure or scope of the response, which is missing.

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?

Schema description coverage is 100%, so the input schema already documents both parameters with descriptions. The tool's description does not add any additional meaning or context beyond what the schema provides, earning a baseline score of 3.

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 clearly states the tool's purpose: looking up RunAPI pricing for a specific model line ('happyhorse'). The verb 'look up' combined with the resource 'pricing' is specific and unambiguous, and it distinguishes itself from sibling tools that handle video editing and task retrieval.

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 context (e.g., before using video editing tools), but it does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. While the tool's purpose is clear from its name and siblings, no explicit guidance is given.

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