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

With no annotations provided, the description bears the full burden of behavioral disclosure. It excels by revealing that this is not a purchase or guaranteed quote, defining consent with the exact text, and disclosing that the enquiry reaches providers only after the person clicks the email link. It also describes step-1 validation and the token hand-off, which are non-obvious behaviors.

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 long but every sentence earns its place. It front-loads the core purpose and then structures the two steps clearly. The quoted consent text removes any ambiguity, and the flow is easy to follow despite the complexity.

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 two-step, human-in-the-loop submission with no output schema, the description is complete. It covers inputs, expected returns (summary, consent line, confirmation token), the user-consent gate, and the email-click requirement. An agent has everything needed to invoke it 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?

Although schema coverage is 100%, the description adds crucial semantics: answers must be keyed by field keys from enquiry_fields, consent means the person has agreed to the exact quoted line, and confirmation is the token produced in step 1. This goes well beyond the schema's structural descriptions.

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 the specific action: submits an enquiry to Industrial Cleaning Quotes. It explicitly distinguishes this from a purchase and a guaranteed quote, and the title reinforces the two-step nature. This clearly separates it from the sibling tools, which are about describing enquiries and fetching field definitions.

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 gives explicit step-by-step usage: call with answers and consent=true, then conditionally call again with the confirmation token. It also references enquiry_fields for answer keys, which orients the agent to the correct companion tool. It does not explicitly name alternatives, but the workflow context is unambiguous.

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