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

With no annotations, the description carries the full disclosure burden, and it does contribute real behavioral context: per-call pricing ($0.001 via x402/USDC on Base) and the presence of a provenance chain and Ed25519 attestation in the response. It still omits the free-quote path (left to the schema), the fact that this is a non-destructive read, and any error/limits behavior, so it is only partially complete for a no-annotation tool.

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 tight sentences with the core capability front-loaded and no filler. The payment/attestation sentence earns its place given the absence of annotations, though it could be trimmed slightly.

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?

There is no output schema, but the description does state the return shape (areas plus rent schedules, provenance, attestation), which partly covers that gap. The missing pieces are the meaning of the required 'q' parameter and routing relative to fmr_area_lookup, leaving the definition merely adequate for a two-parameter lookup tool.

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 only 50%: the required 'q' parameter has no schema description, and the description does not compensate by explaining its matching semantics (substring vs exact, case handling, 80-char cap). Only the optional 'payment' parameter is documented, and only in the schema, not the description.

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?

The description gives a specific verb (Search) and resource (HUD Fair Market Rent areas), plus the match criterion (by name) and the shape of the result (matching areas with rent schedules). It does not, however, differentiate itself from the sibling fmr_area_lookup, which an agent could plausibly confuse with a name-search tool.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no mention of the sibling fmr_area_lookup as the alternative for exact/ID-based retrieval. Usage must be inferred from the name and description alone.

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