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

With no annotations provided, the description carries full behavioral disclosure. It explains that this is not a purchase, not a guaranteed quote, requires two calls, returns a summary and confirmation token, requires the person to agree before the second call, and that an email link click is needed before providers see the enquiry. It even quotes the exact consent text.

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 most important caveat ('NOT a purchase'), then lays out Step 1 and Step 2 in a logical, structured way. The exact consent line is included because it is operationally required.

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?

There is no output schema, so the description compensates by explaining exactly what Step 1 returns (summary, consent line, confirmation token) and what happens after submission (email with clickable link, then provider visibility). This is complete enough for an agent to execute the tool safely and 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 the schema already documents all parameters at 100% coverage, the description adds critical semantics: answers must be keyed by field key from enquiry_fields, consent must be true and match the quoted consent text, and confirmation must be the token from step 1. This meaningfully clarifies how the parameters connect in the two-step flow.

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 ('Submits an enquiry to Texas HVAC Replacement Cost') and immediately distinguishes itself from a purchase or guaranteed quote. It also clearly separates the two-step submission workflow, making the tool's purpose unmistakable even among sibling tools.

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 clear step-by-step usage context: call once with answers and consent, show the summary and consent line, then call again with the confirmation token only if the person agrees. It does not explicitly name alternative tools or state when not to use it, but there is no real submission alternative among the siblings.

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