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

With no annotations, the description carries the full disclosure burden and does so well: it explains that step 1 only validates and returns a summary, consent line and token, that nothing is submitted until step 2, and that the submitter must click an emailed link before any provider sees the enquiry. It also defines exactly what consent means. Only minor gaps remain (idempotency/rate behavior) but the critical side effects and gating are covered.

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?

Front-loads the most decision-relevant fact ('NOT a purchase, NOT a guaranteed quote') and then walks the two steps in order. It is information-dense and every clause is load-bearing, though the enumerated consent sentence and bolded emphasis make it longer than the minimum.

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 tool with no output schema, the description compensates by describing what step 1 returns (summary, consent line, token) and what happens after step 2 (confirmation email before providers see it). Combined with the nested `answers` object, an agent has everything needed to perform the interaction 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 description coverage is 100%, so the schema already documents all three parameters, making 3 the baseline. The description reinforces the meaning of consent and the confirmation token in the workflow, but adds little beyond what the schema's own descriptions and the 'field key from enquiry_fields' note provide.

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?

Names a specific verb and resource ('Submits an enquiry to Answering Service Quotes') and immediately carves it away from adjacent concepts by stating it is NOT a purchase and NOT a guaranteed quote. An agent knows exactly what this tool does before reading the schema, and its two-step nature separates it from the read-only dataset_*/enquiry_* discovery siblings.

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?

Spells out the calling sequence: Step 1 with answers plus consent=true to validate, Step 2 only if the person agrees, passing the same answers plus the confirmation token. It also states the consent precondition explicitly, so the when-to-use and when-not-to-proceed conditions are unambiguous.

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