Quote an exact SpicyAPI request

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds further useful behavior: it creates no task, reserves no funds, and returns a five-minute USD estimate plus maximum charge. This goes beyond what annotations alone convey.

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?

Three short sentences, each earning its place: one states the core action, one states the returned data, and one prevents misuse. The most important differentiator is front-loaded.

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 the read-only annotations and presence of an output schema, the description covers the critical behavioral and usage context well. The main gap is parameter semantics, especially for the nested input object and optional callBackUrl, but the overall tool purpose remains clear enough for an agent to use correctly.

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%, so the description carries the full burden for parameter meaning, but it never mentions model, input, or callBackUrl. The phrase 'exact request price' hints that input represents the request, but the tool does not explicitly explain what each parameter is or how it shapes the quote.

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 states a specific action ('Compare an exact request price'), the resource (an exact SpicyAPI request), and key constraints ('without creating a task or reserving funds'). It clearly differentiates this from task_create and other task-related siblings.

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 explicitly tells the agent not to call this as a routine prerequisite because task_create already obtains its own quote and confirmation. It also implies the tool is for price comparison before deciding to create a task, giving clear usage context.

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