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

With no annotations, the description carries the full burden and does well: it discloses that step 1 only validates and returns a token, that the enquiry is submitted only in step 2, and that an email link must be clicked before any provider sees the data. It also enumerates the consent scope (up to three specialists, notification per firm, opt-out). It stops short of stating error/validation-failure behavior or idempotency of a repeated step 2 call.

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?

Well front-loaded — the non-purchase disclaimer and the step framing lead. It is dense but nearly every clause is operational. The one redundancy is the consent sentence, quoted verbatim from the schema's consent description, which repeats rather than extends structured data.

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?

No output schema exists, so the description must describe returns, and it does: a summary, the consent line, and a confirmation token from step 1. For a two-phase, nested-object tool that triggers third-party data sharing, this covers what an agent needs to call 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: 'answers' are keyed by field key sourced from enquiry_fields, 'consent' must be true to proceed, and 'confirmation' is explicitly the token returned from step 1 after approval. That sequencing context is not derivable from the schema alone.

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 names a specific verb and resource ('submits an enquiry to Render Cost Calculator') and immediately disqualifies the two likeliest misreadings: 'NOT a purchase, NOT a guaranteed quote.' That framing cleanly separates it from siblings like calculate and enquiry_fields.

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 ordered procedure: Step 1 with answers and consent=true, Step 2 'only if the person agrees' with the same answers plus the confirmation token. The gate condition for the second call is stated, not implied, and the surrounding agent obligations (show the summary and consent line) are spelled out.

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