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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety and determinism profile is fully covered. The description usefully adds a substantive domain fact (the entity is a brokerage that arranges financing and is not a lender; owner-occupied loans are excluded), but says nothing about caching, determinism, or how the answer is sourced.

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 dense sentence that front-loads the entity and then lists the returned fields; no filler or repetition. It is long but every clause maps to a concrete piece of the answer.

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, the description effectively serves as the return contract by enumerating the fields the entity answer provides. For a zero-parameter, read-only lookup this is complete enough for an agent to decide and call it.

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?

The tool takes zero parameters, so the baseline is 4; there are no inputs whose semantics need explanation.

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 resource (the National Loan Provider entity) and enumerates exactly what the answer contains — legal name, business model, scope, address, phone, states with data, founder @id. This is clearly distinguishable from siblings like glossary_lookup, hmda_methodology, or rate_ranges without opening any 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?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the six sibling tools. The agent must infer from the content list alone that this is the identity/background tool rather than a data or definition tool.

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