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

With no annotations, the description carries the full behavioral burden and does well: it discloses validation on step 1, the returned summary/consent line/token, the double-submit requirement, and the post-submit email-verification gate before any provider sees the data. It also discloses the downstream data-sharing scope (up to three agencies, email notification per firm, ability to stop). What it does not state is error/failure behavior (e.g. what happens on an invalid answer set or an expired token).

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-loaded with the critical 'NOT a purchase' framing and then cleanly organized as Step 1 / Step 2, so it scans well. The full verbatim consent paragraph is repeated in the schema's consent description, which is some redundancy, but it is arguably load-bearing for a consent-critical tool.

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, yet the description explains what each call returns (summary, consent line, confirmation token) and what happens after submission. Combined with 100% schema coverage and the explicit consent semantics for the nested answers object, an agent has everything needed to drive the two-step flow 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 genuine meaning: answers are keyed by field key sourced from enquiry_fields, consent must be true for step 1, and confirmation is only supplied on step 2 after human approval. That sequencing constraint 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?

States a specific verb and resource ('Submits an enquiry to Trades SEO Agency') and immediately scopes it with two negations ('NOT a purchase, NOT a guaranteed quote') that prevent the most likely misclassification. It also names the sibling that supplies the input keys (enquiry_fields), so an agent can route correctly without opening another schema.

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?

Gives an explicit two-step protocol: Step 1 with answers + consent=true to validate and obtain a token, Step 2 only if the person agrees, with the same answers plus the token. The gating condition ('only if the person agrees') and the required human action (show the summary and consent line) are stated, not implied.

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