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

With no annotations, the description carries the full burden and does so: it discloses that step 1 is validation-only, that a confirmation token gates the real submission, that the person must click an emailed link before any provider sees the data, and that details go to up to three chosen consultants. It also spells out exactly what consent means, which is critical for an irreversible disclosure of personal data.

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 front-loaded with the most decision-relevant fact ('NOT a purchase') and each sentence adds protocol detail. The main inefficiency is restating the consent text verbatim, which the schema's consent field already documents, creating duplication.

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 two-step, nested-object tool with no annotations and no output schema, the description covers everything an agent needs: what step 1 returns (summary, consent line, token), what step 2 does, and the downstream email-confirmation gate. Nothing material 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 baseline is 3, but the description adds genuine meaning beyond the schema: it explains that answers are keyed by field key sourced from enquiry_fields, and that the same consent/answers must be resent in step 2 alongside the confirmation token. That clarifies the temporal relationship between parameters that the schema alone does not convey.

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 (submits) and resource (an enquiry to ISO Certification Cost), and immediately distinguishes itself from siblings and from adjacent concepts by ruling out 'NOT a purchase, NOT a guaranteed quote.' An agent can tell this apart from enquiry_describe/enquiry_fields without opening any 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 call with answers + consent=true to validate and obtain a token; step 2 only after the person agrees, calling again with the token. It states the precondition for each call and what must be shown to the person in between, leaving nothing to inference.

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