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

No annotations exist, so the description carries the full burden, and it does: it discloses the two-phase validation-then-submit flow, the confirmation token, that an email requiring a click precedes any provider seeing the data, that up to three providers are sent the details, and the exact consent meaning. That is far more than the parameter schema conveys.

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 disambiguation and the step structure, and nearly every clause carries operational content. It is long, and the verbatim consent text duplicates the consent parameter description in the schema, which is a minor 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?

With no output schema and no annotations, the description must explain return behavior, and it does: step 1 returns a summary, consent line and confirmation token; step 2 submits and triggers a verification email. Nothing needed to call the tool correctly 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 coverage is 100%, so the baseline is 3. The description adds real meaning on top: answers must be 'keyed by field key from enquiry_fields', consent must be true, and confirmation is the token returned in step 1 rather than an arbitrary string. Only the value types of answers are left to 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 verb (submits) and resource (an enquiry to Lease Renewal Cost) and immediately disambiguates what it is not: 'NOT a purchase, NOT a guaranteed quote.' This contrast is what makes it easy to separate from a purchase or quote tool.

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 with the exact conditions for each call: step 1 validates and returns a token, step 2 only fires 'if the person agrees' and requires the token. It also specifies what to show the user (summary + consent line) before proceeding, 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.