Get Market Statistics

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

With no annotations provided, the description carries the full burden. It discloses return behavior (summarized snapshot, omitted blocks when data is sparse), currency units (USD, rents per month), and data_type effects. It doesn't cover rate limits or auth, but these are likely common to all tools. The core behavioral aspects are well covered.

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 five sentences, front-loaded with the tool's purpose, then usage guidance, then return semantics. Every sentence earns its place; there is no redundancy or filler.

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 there is no output schema, the description offers a complete picture: what metrics are returned, the units, how data_type affects output, and what happens when data is insufficient. For a moderate-complexity stats tool, this is fully sufficient.

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 input schema covers all parameters with descriptions (100% coverage), so baseline is 3. The description adds value by clarifying data_type options ('sale stats, rental stats, or both') and the purpose of zip_code as a geographic baseline. history_range is not explicitly described in the description, but the schema covers it adequately.

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 tool's function: 'Get aggregate market statistics and trends for a ZIP CODE' and lists specific metrics (sale/rent prices, days on market, etc.). It is distinct from sibling tools, which focus on individual properties or listings, and even mentions a sibling (get_rent_estimate) for comparison.

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 explicitly says when to use the tool: 'Use this to establish the local baseline' and gives concrete examples (comparing a property's rent estimate, gauging whether an area is hot). It does not include explicit when-not-to-use or alternative tools, but the context is clear and actionable.

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