hud_fair_market_rents

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

Annotations declare readOnlyHint=true, and the description's 'Get' is consistent. It adds useful context about the output (efficiency through 4-bedroom) and the tool's purpose (FMR determines Section 8 amounts), exceeding the minimum for a read-only 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?

Three short sentences, each earning its place: action and scope, output shape, and policy context. No redundancy or fluff.

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 simple read-only tool with no output schema, the description conveys core functionality and output (rent by bedroom count). It relies on the schema for parameter details, which is acceptable given 100% coverage. It does not mention when to use it vs. related tools, but that is covered under usage guidelines.

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% with parameter descriptions. The description gives a high-level overview of location scoping (county/metro/state) but does not add significant new meaning beyond the schema's parameter descriptions. 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?

The description clearly identifies the verb 'Get' and resource 'HUD Fair Market Rents' with scoping options (county, metro area, or state). It specifies the output (monthly rent by bedroom count), but does not explicitly distinguish from related tools like hud_income_limits or hud_list_states.

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?

Provides clear context on what locations are supported (county, metro, state) and notes the policy relevance (Section 8 voucher amounts). Does not explicitly state when to use this tool over alternatives, but the scoping guidance is clear enough for an agent to select it for FMR queries.

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