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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the completeness guarantee ('every specialty', i.e. no filtering or pagination) and notes that supported languages are included, which is modest extra context rather than rich behavioral disclosure.

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 usage condition, followed by the return contract; both sentences earn their place. The long enumeration of example specialties (FHA, VA, USDA, jumbo, DSCR...) is helpful for semantic matching but is the wordiest part of the definition.

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 zero-parameter, read-only listing tool with full annotations and an output schema, the description supplies everything an agent needs: when to call it, that the result is exhaustive, and the shape of each entry. Return-value detail is technically redundant with the output schema but does not leave any gap.

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 schema carries no semantics to clarify and the baseline of 4 applies. Nothing in the description is needed or misleading on this dimension.

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 ('Returns every specialty') and enumerates exactly what comes back: slug, category, label, one-line description and canonical_url. The scope word 'every' plus the use-case framing ('the mortgage situations LenDb can match on') separates it from the single-item sibling explain_specialty without the agent needing to open either 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?

'Use this when you need the mortgage situations LenDb can match on' gives an explicit trigger condition. However, it never names an alternative (e.g. explain_specialty for one specialty) or states when not to use it, so the routing guidance is clear but not complete.

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