check_pricing

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

No annotations provided, so the description must disclose behavioral traits. It only says 'look up pricing,' implying a read-only operation, but does not explicitly state no side effects, authentication needs, or rate limits. For a tool that queries pricing, more transparency (e.g., 'this tool does not modify any data') would be beneficial.

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 with no extraneous information. It directly states the tool's function without any filler, achieving maximum conciseness.

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 no output schema and low tool complexity (2 optional enum parameters), the description is too sparse. It does not explain what the pricing lookup returns (e.g., cost per unit, subscription info), nor does it mention default behavior for unspecified parameters. Sibling tools are action-oriented, but for a pricing tool, more context about the output format or usage scenarios is needed.

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 coverage is 100%, and the description mentions 'midjourney model line' which aligns with the model parameter's enum values, but it does not add any meaning beyond the schema. The schema already documents model and action with descriptions and defaults. Baseline 3 is appropriate since description adds no extra semantic value.

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?

Description clearly states the tool's purpose: 'Look up RunAPI pricing for the midjourney model line.' This is a specific verb ('look up') and resource ('pricing'), and it scopes to the midjourney model line, distinguishing it from sibling tools that perform actions like image generation or editing.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for pricing lookups, but does not state when not to use it or suggest other tools for similar purposes. Sibling tools are all action-oriented, so the usage is somewhat implied, but lack of explicit guidelines keeps it at a 3.

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