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

Annotations already declare write, non-destructive, open-world, so the safety profile is covered. The description adds genuine value beyond that: it declares the write is gated on user confirmation and sets negative expectations ('does not return a credit offer or an approval'), which prevents an agent from misreading the response.

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?

Three short sentences, front-loaded with the action and scope, then prerequisites, then the return-value caveat. Every sentence carries distinct information with no restatement of the title.

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 17-parameter write tool with no output schema, the description covers the action, gating condition, and response expectation. The remaining gap is the alias-heavy parameter surface (lender/lenders/providers, product/productType), which the description does not disambiguate even though the schema does.

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 88%, so the schema already documents applicant fields, lender/provider shapes, and the confirmed flag. The description restates the required fields rather than adding new semantics (e.g. it never explains when to use lender vs lenders vs providers, or how 'confirmed' interacts with submission).

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+resource ('Create a user-confirmed enquiry'), names the target ('one selected lender'), and states the return ('application record'). 'One selected lender' implicitly distinguishes it from the sibling create_multiple_lender_enquiries.

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 a clear precondition (user confirmation, with required first name, last name, email; phone optional) and the single-lender scope that separates it from the multi-lender sibling. It stops short of explicitly saying when to prefer create_multiple_lender_enquiries or trace_offer_status, so it is context-clear but not a full routing rule.

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