get_price

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

Adds real behavior beyond the readOnly/openWorld annotations: it advertises the disputed=true disagreement signal, a close-matches fallback for unknown models, and provenance via source and last-confirmed date. It stops short of saying whether the base price is an average or a preferred source when sources agree.

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?

Two sentences, no filler. The primary capability is front-loaded and the routing note trails it, which is the right ordering.

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?

With no output schema, the description carries the return-value burden and does so for the headline fields (price, unit, source, date, disputed, close matches). What the close-match payload looks like and how ambiguity is resolved is left implicit.

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?

Only one parameter and schema coverage is 100%, with the schema already giving id-or-name examples. The description adds unit framing for the returned price but nothing about model_name syntax or edge cases (aliases, versions), so baseline 3 applies.

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?

States a specific verb and resource ('List price for one LLM') plus the unit basis (USD per million tokens), which immediately separates it from estimate_cost and find_cheaper. An agent knows exactly what it retrieves without opening the schema.

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?

Explicitly redirects workload costing to estimate_cost, giving a clear when-not-to-use condition. It says nothing about find_cheaper, so the sibling triage is only two-thirds complete.

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