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

Goes well beyond the annotations by disclosing the full async workflow: voidjet emails a link, nothing reaches the provider until the user opens it within 48 hours, and prices are indicative. The annotations cover safety/idempotency, and the description layers on the real behavioral mechanics an agent needs.

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?

Front-loads the purpose and workflow, and every sentence adds distinct information. It is dense and slightly run-on, but there is no filler.

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 an output schema present, return values need not be explained, and the description fully captures the inquiry workflow and the nature of the optional fields. The remaining gap is the undocumented required/behavioral parameters (ref, passengers, flexible).

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 carry weight. It clarifies that name, phone and message are optional, user-sourced, and only pre-fill the form — useful meaning — but leaves ref, passengers, locale and flexible unaddressed.

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 ('Prepares an inquiry for one offer') and scopes it to a single offer. It reads clearly against siblings like request_charter_quote and create_flight_alert, though it doesn't explicitly name any of them.

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 a concrete precondition for use: 'for when the user has asked to inquire and given their email.' This is a clear triggering condition, but it names no alternatives or when-not cases against the sibling tools.

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