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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing the paid-call model — $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. That billing detail is material to invocation (an agent should avoid wasteful calls) and is not in the schema. It says nothing about rate limits, response paging behavior, or coverage freshness, but with read-only annotations those omissions are minor.

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?

The opening clause is well front-loaded (what it is, where, what it returns), but the 20-field output enumeration is largely redundant because an output schema exists, and it inflates the front of the description. The two sibling call-outs and the price sentence are useful, yet both sibling sentences are garbled/truncated ("forfeited real", "US city: property"), which reads as sloppy extraction rather than deliberate brevity.

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 four simple parameters, full schema coverage, an output schema, and read-only/open-world annotations, the description covers the remaining essentials: exactly what inventory this is, geographic scope, that it is a paid x402 call, and which siblings to prefer for adjacent needs. Only coverage/refresh behavior and result-size behavior remain unstated, which is acceptable given the output schema.

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 100%, so the baseline is 3; the schema already explains state as a 2-letter code, optional city, limit 1-200 default 50, and maxPrice in USD. The description only echoes "in a US state or city" and adds no format or constraint detail beyond the schema. The long field enumeration describes return values rather than parameter meaning.

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 states a specific resource and scope: HUD Home Store FHA-foreclosure inventory for online bid, filtered to a US state or city, and it reconciles the confusing tool name by noting it replaces Auction.com. It also enumerates the returned fields (case number, list price, beds, status, bid dates), so an agent knows exactly what data comes back. The sibling-comparison clauses are truncated mid-sentence ("upcoming U.S. Treasury auctions of seized/forfeited real"), which slightly blunts precision.

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?

It explicitly routes two alternative needs to named siblings: Treasury/seized-auction data to realestate_auction_com_property_scraper_ppe, and rental listings to realestate_apartments_com. It does not address the many other real-estate siblings (zillow, realtor, redfin, realtytrac, homed) that also cover US listings, so an agent must infer that this tool is specifically the HUD/FHA-foreclosure channel. Clear context, but no explicit when-not-to-use beyond the two named alternatives.

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