create_quote

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

With no annotations, the description carries the full burden. It discloses the return value (quoteUrl), the lifecycle (open until paid, cancelled, or expired; default 30 days), and that it appears in the dashboard. However, it does not mention permission requirements or failure modes, which keeps it from a 5.

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 front-loaded with the main purpose, then provides key outcome details and input requirements in a structured way. It's longer than minimal, but each section adds necessary context for a complex 12-parameter tool.

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 the tool's complexity, the description covers the core concept, outcome, required/optional inputs, and lifecycle. It lacks detailed parameter semantics and doesn't always connect to schema, but overall it gives sufficient context for correct use.

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 coverage is only 25%, so the description must compensate. It lists all required and optional parameters and clarifies the tags format (array of {key, value} objects), but does not explain semantics for fields like netTermsDays or fulfillmentTerm, leaving gaps.

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 creates a new quote (formal order document) for FastSpring SKUs, and distinguishes it from checkout sessions by explicitly saying it does not charge the buyer. It also positions it as the correct way to generate a Custom Order, which differentiates it from the read/update sibling tools.

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?

It provides explicit guidance on when to use (to generate a Custom Order/quote) and when not (not a checkout session, does not charge). While it doesn't name an alternative tool, no creation alternative exists among siblings; the exclusion of charging behavior is a clear when-not.

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