Get one SpicyAPI model

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds non-obvious behavior: the returned input schema is plain JSON Schema with display-only and rate-card annotations stripped, and some input values affect price. That is real context beyond the annotations.

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?

Four sentences, front-loaded with the return payload before the reuse and pricing caveats. Each sentence adds a distinct fact (what returns, when to reuse, schema shape, pricing guidance) with no filler, though the pricing sentences are slightly dense.

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?

An output schema exists, so return-value detail is unnecessary, and the description correctly focuses on reuse strategy, schema preprocessing, and pricing interpretation. The only gap is the format of the required 'model' argument, which neither schema nor description supplies.

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 0% and the single 'model' parameter has no description in the schema, so the description carries the full burden. It only says 'one exact model', never stating the identifier format, source, or whether it accepts an id, slug, or name. It does not compensate for the coverage gap.

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 ('Return one exact model') and enumerates the payload dimensions it returns: input schema, pricing, policy, availability. It also names the sibling models_list, so an agent can distinguish a single-record fetch from the list tool without opening either 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?

Gives clear routing: reuse a complete record from models_list with includeSchema rather than re-fetching, and use task_create for the exact request quote. It also advises using pricing entries for comparisons instead of computing the charge. It stops short of stating when this call is mandatory versus optional (e.g. staleness tolerance).

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