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

No annotations are provided, so the description carries the full burden. It discloses the two-step validation flow, the need for a confirmation token, the exact consent wording, and that the person receives an email with a link that must be clicked before providers see the enquiry. This is highly transparent behavior beyond the schema.

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 structured with Step 1 and Step2, front-loaded with the core purpose and the purchase caveat. Every sentence contributes procedural or consent information; there is no filler or redundancy.

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?

This is a complex two-step mutation tool with no output schema and no annotations. The description covers validation behavior, the intermediate response (summary, consent line, token), the required second call, and the email-link condition before providers see the enquiry. An agent has all necessary context to invoke both steps 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 baseline is 3. The description adds meaningful step-specific semantics: answers must be keyed by field key from enquiry_fields, consent must be true only when the person agreed to the exact consent text, and confirmation is the token from step 1. This elevates the parameter understanding beyond 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 the specific verb 'Submits' and resource 'enquiry to Commercial Mortgage Calculator', then immediately clarifies it is 'NOT a purchase, NOT a guaranteed quote', distinguishing it from purchasing or quoting tools. The two-step nature and resource are also reflected in the title, making the tool's role unmistakable.

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 explicit step-by-step usage: Step 1 call with answers and consent=true to get a summary and token; Step 2 call again with the token only if the person agrees. Also gives when-not guidance ('NOT a purchase, NOT a guaranteed quote') and the exact consent condition. It does not explicitly name sibling tools like enquiry_fields, but the procedure is clear enough to guide correct invocation.

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