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

With no annotations present, the description carries the full burden, and it delivers. It discloses that the quote is binding, valid for 30 minutes, returns an exact price, and is a mandatory prerequisite for charging. This goes well beyond the schema and tells the agent what behavioral consequences to expect.

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 three tight sentences with no fluff. The core action and key constraint are front-loaded, and every sentence earns its place by providing either the action, the return contract, or the mandatory usage context.

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?

Despite lacking an output schema and annotations, the description provides everything an agent needs to call the tool correctly: what it does, what it returns (quote_id, exact price), how long the quote is valid, and the mandatory ordering relative to other tools. No critical invocation detail is missing.

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 100%, so the schema already documents each parameter thoroughly. The tool description does not add meaning to individual parameters beyond what is in the schema. Baseline 3 applies because the schema is doing the heavy lifting.

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 ('Issue a BINDING quote'), identifies the resource ('for a slot'), and names the key return value (quote_id and exact price). It also distinguishes itself from sibling tools by explicitly referencing create_ad_order and create_checkout_session as downstream steps, making its role clear.

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 gives explicit when-to-use guidance: 'You MUST call this before create_ad_order or create_checkout_session.' It explains why this ordering matters by noting that the quote_id is the only thing that authorizes a charge. This is direct, actionable guidance for selecting and sequencing the call.

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