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

Adds substantial behavior beyond the annotations: the agency calls back within one working day and there is a hard limit of 3 requests per day (a rate constraint no annotation expresses), plus a personal-data consent requirement. It does not explain the idempotentHint=true semantics (retry safety), which is the one behavioral trait left implicit.

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?

Four tight sentences, front-loaded with the action, then the required inputs, then the callback expectation and rate limit. Every sentence carries information the agent needs; nothing is padding.

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 9-parameter mutation with no output schema, the description covers the important unknowns: prerequisites (name, phone, consent), turnaround time, and the per-day cap. What it omits — what the confirmation/response contains — is minor since a callback-based flow has little to return.

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% across all 9 parameters, so the schema already carries field-level meaning; baseline is 3. The description reinforces that name and phone are the two required inputs and that the request may target one venue or a selection, but adds no format or syntax 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?

States a specific verb+resource (send a request to the agency to check a venue's availability and receive a quote), including both variants: a single venue or a curated selection. It is clearly distinguishable from the read-only siblings (search_venues, get_venue, list_*), which only look things up.

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 clear context for use — availability check plus quote — and the prerequisite that name and phone must be collected with the user's consent before sending. It references the venue slug coming from search_venues in the schema but does not explicitly say when to prefer this tool over just browsing with search_venues.

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