get_pricing

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

With no annotations provided, the description carries the behavioral burden. It tells the agent this is a read-only, machine-readable data retrieval operation returning current pricing, not a human-facing report or a mutating action. It does not mention auth or rate limits, but those are less critical for a simple pricing lookup.

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 filler. The key facts — 'current', 'price list', 'bigapi.dev', and 'machine-readable' — are front-loaded and each adds meaningful information.

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 zero-parameter, read-only pricing tool, the description gives enough context to select and invoke it correctly. There is no output schema, but 'price list' is self-explanatory and 'machine-readable' signals the expected output form. Auth behavior is not disclosed, but that is a minor omission for 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?

The input schema has zero properties and schema description coverage is 100%, so there are no parameters to document. The description appropriately does not invent parameters or imply that arguments are needed, which is correct for this tool.

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 returns the current price list for bigapi.dev, using a specific resource ('price list') and operation ('get'). It also distinguishes itself from siblings like get_usage, get_access, and get_balance, since none of those named tools are explicitly about pricing.

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 the correct use case: whenever the agent needs the current pricing information for bigapi.dev. It does not explicitly list alternatives or exclusions, but the use case is unambiguous and the zero-parameter nature of the tool reduces the risk of misuse.

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