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

The description adds substantial context beyond the annotations: nothing is offered or agreed, the buyer receives a confirmation link, the message is delivered only after confirmation, and the representative replies directly. It also discloses the needs_answers qualification flow, which is important behavioral information for an open-world contact tool.

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 core action and then adds only necessary preconditions and workflow details. Each sentence contributes to correct invocation, with no redundant 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 no output schema, the description still explains the key response behavior: the buyer gets a link, delivery waits for confirmation, and the representative replies directly. It also covers the qualification-question branch, making the workflow complete enough for an agent to call the tool 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 100%, so the schema already documents all seven parameters, including name, email, message, and answers. The description reinforces some parameter meaning, such as using the person's own details and answering qualification questions in order, but it adds little beyond the schema.

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 verb and resource: it passes a would-be buyer's message to the owner's acquisition representative for one aircraft. This is clearly distinct from the sibling tools, which are about searching, availability, charter estimates, or requesting trips.

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 gives an explicit precondition: call only after the person has asked to contact the owner and has provided their own name, email, and message. It also explains the two-step qualification-question flow, so the agent knows when a second call is required.

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