Get a homes.com market report for a location

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

The description adds significant value beyond annotations by noting the tool returns a sample of ~40 listings, the summary is not an exhaustive market index, and explicitly states 'Read-only'. This compensates well for the existing readOnlyHint and idempotentHint annotations.

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 description is concise (3 sentences) and well-structured: purpose, parameter usage, return structure, and a caveat. Every sentence adds value, and the key information is front-loaded.

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?

Given no output schema, the description clearly outlines return fields (region, slug, sold_summary, sample_sold) and explains that sold_summary includes count, median sale price, and average $/sqft. The sample-size caveat provides essential context. Annotations complement well.

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 single parameter 'location' is fully described in the schema (100% coverage). The description provides example values but does not add new semantic or syntactic details beyond the schema description. Baseline score of 3 is appropriate.

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 states the verb 'Fetch and derive', the resource 'recently-sold listings' and 'market summary', and specifies the output structure. It distinguishes itself from siblings like homes_search_properties by focusing on market summary from sold data.

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?

The description explains how to use the tool (pass location as free-text) but does not explicitly state when to use this tool vs. alternatives like homes_search_properties or when not to use it. The context is clear but lacks exclusionary guidance.

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