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

With no annotations, the description carries the full burden and handles it well. It discloses the two-step stateful behavior, validation, confirmation token, consent line, email delivery, and the fact that a provider sees nothing until the person clicks the link. This goes far beyond a typical 'submits an enquiry' description.

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 longer than average, but every sentence earns its place: the step numbering keeps the protocol readable, the exact consent line is critical, and the exclusions prevent misuse. It is front-loaded with the action and the most important caveat. The only minor cost is density, not waste.

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, no annotations, a nested answers object, and a subtle two-step contract, this description is unusually complete. It tells the agent exactly what to send in each step, what to show the person, what token to carry, what consent means, and what happens after submission. Nothing essential is missing.

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 baseline is 3. The description adds meaning beyond the schema by explaining how each parameter participates in the workflow: answers are keyed from enquiry_fields, consent has an exact quoted agreement, and confirmation comes from step 1 only after approval. This is useful value above 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 action ('Submits an enquiry'), a clear resource ('to AI vs Hire'), and a precise two-step workflow. It also explicitly distinguishes itself from a purchase or guaranteed quote, and the title reinforces the scope. This is enough to separate it from sibling tools 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?

Provides clear step-by-step guidance: call once to validate and get a token, then call again only if the person agrees. It also states exclusions ('NOT a purchase, NOT a guaranteed quote') and the consent precondition. It does not explicitly name sibling alternatives for when NOT to use this tool, but the usage context is otherwise exceptionally clear.

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