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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is mainly to describe the payload, which it does in detail (unit counts, financing type breakdowns, weighted 2026 rent). It omits what happens on a partial/ambiguous name match or a failed lookup, which matters with no output schema and all-optional params.

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?

Two sentences: the first front-loads the resource and its contents, the second covers identification inputs. Dense but each clause carries information; the long field enumeration is slightly list-heavy but not padded.

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 does the necessary work of telling the agent what comes back, and it explains input alternatives for a zero-required-param tool. Missing only edge-case behavior (ambiguous name, unknown code) that an agent would want before calling.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it signals that code, url, and name+state are interchangeable identification routes and that name pairs with state. Examples (IL002, rad.loans page URL) reinforce the expected formats.

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?

Names a specific resource (a single housing authority's RAD record) and enumerates exactly what that record contains: closed conversions with units/PBV/PBRA/tax credits/FHA, CHAP-to-closing deals, remaining public housing units with weighted 2026 RAD rent, and a conversions list. It is clearly a single-entity lookup rather than a search, which implicitly separates it from search_conversions, but no sibling is named explicitly.

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 concrete invocation guidance: 'Give the HUD PHA code (IL002), the rad.loans page URL, or name + state,' which is valuable because all four params are optional and an agent otherwise wouldn't know which key to supply or that name needs a state alongside it. It stops short of saying when to prefer this over search_conversions or get_rad_rents.

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