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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that, reinforcing it with "Does not submit a request." That negative-scope statement is real added value beyond the annotations, since it prevents the agent from assuming a side effect. It does not describe the shape of the returned form, but with no output schema and a trivial zero-parameter surface, that gap is minor.

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?

Two short sentences with zero filler, front-loading what is retrieved and following with the key negative scope. Nothing is repeated from the schema or annotations.

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 a zero-parameter, non-destructive read tool with no output schema, the description supplies everything needed to decide to call it and what to expect conceptually (a request form and details). Only the exact form of the returned content is left unspecified, which is acceptable given the tool's simplicity.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a no-parameter schema applies. The description correctly implies no inputs are needed by framing the call as simply retrieving form material.

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?

"Get the request form and details needed for a verified private coach quote" names a specific verb (get) and a specific resource (quote request form/details), so the purpose is unambiguous. It does not explicitly contrast itself with the sibling list_charter_countries / list_charter_vehicles tools, but those cover clearly different resources, so misselection risk is low.

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 establishes context (preparing a verified private coach quote) and sets an explicit boundary with "Does not submit a request," telling the agent this is a preparatory step rather than an action. It stops short of naming the hypothetical submit tool the agent should use afterward, so the alternative is implied rather than stated.

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