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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on real behavioral context: US-only scope, the meaning of disciplinary_check='not_checked', the last-verified date, and an explicit statement that phone/email are withheld pending human check. That is meaningful disclosure beyond what the structured fields provide.

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 usage trigger is front-loaded and the response inventory is packed into one dense sentence with no filler. It is on the long side and the field enumeration reads as a run-on, but every clause conveys usable information.

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 single-parameter lookup tool this is complete: it covers the identity model, geographic scope, data provenance ('LenDb's sourced record'), known gaps (no phone/email, unchecked discipline), and freshness. The output schema exists, so the return-field listing is a bonus rather than a necessity.

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% and the single parameter is fully documented in the schema (digits only, example 452476). The description only restates that the ID is the individual officer's NMLS ID, adding marginal meaning over the schema — 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 and resource ('Get a loan officer') keyed by the identifying attribute ('by NMLS ID'), which cleanly separates it from the sibling find_loan_officers search tool and from get_lender. An agent knows exactly what entity this returns without opening the 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 a clear trigger condition: use it 'when you have a mortgage loan officer's individual NMLS ID and need their full profile' — implying a known-ID lookup rather than a search. It does not explicitly name find_loan_officers as the alternative for name/state lookups, so the routing guidance is implied rather than stated.

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