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

Annotations already declare readOnlyHint=false, openWorldHint=true, non-idempotent and non-destructive, so the safety profile is pre-supplied. The description usefully adds that a live external POST to uqual.com/api/seo-leads is made and that consent is mandatory, but says nothing about what happens on failure, retries, or duplicate submissions despite idempotentHint=false.

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?

A single sentence, front-loaded with the opt-in qualifier before the action and endpoint. No filler and nothing buried.

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 an 11-parameter, nested-object, externally-firing tool with no output schema, the description leaves the return value completely unspecified — an agent cannot tell whether a success confirmation, lead ID, or error shape comes back. The consent gate and endpoint are covered, but outcome expectations are not.

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?

With 100% schema description coverage, the schema already documents all 11 parameters, including the conditional contact-field requirements and the dryRun flag. The description adds no parameter-level meaning beyond what the schema states, so the baseline 3 applies.

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 ('request a review'), a concrete resource ('1-on-1 UQUAL Loan Readiness Coach review'), and the destination endpoint (uqual.com/api/seo-leads). This is unmistakably distinct from the six sibling tools, all of which are local calculators rather than external lead handoffs.

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?

The description gives a hard gate: invoke ONLY when the user explicitly consents to share contact details, which is a clear when-to-use and implicitly a when-not. It does not name an alternative action (e.g., continue with the calculators if consent is withheld), so routing guidance is strong but not exhaustive.

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