get_market_summary

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

There are no annotations, so the description carries full burden. It lists output metrics but does not disclose key behavioral aspects such as behavior when no filters are supplied, whether any parameters are required, data freshness, or the geographical scope of the statistics. For a stats tool, this is insufficient.

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 a single, efficient sentence with the key output metrics front-loaded. It could be slightly more informative by mentioning listing_type, but it contains no unnecessary words.

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?

The tool has no output schema and sparse parameter documentation. The description fails to explain what the return payload looks like, how optional parameters affect results, or whether the statistics are limited to a specific market. This is a significant gap for a summary tool with complex filtering.

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 20% (only 'city' has a description). The description adds meaning for city and property type but omits important filters like listing_type (sale vs rent), country, and neighborhood. It does not compensate for the schema's sparse parameter documentation.

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 explicitly states the resource ('market summary') and the specific statistics returned (average price, median, price per m², listing counts). It clearly differentiates this tool from sibling tools like search_listings, which return individual listings rather than aggregated statistics.

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 phrase 'Filter by city and property type' provides clear context for typical usage, implying this tool is for obtaining market statistics with optional filters. However, it does not explicitly contrast with alternatives like search_listings or state when not to use it.

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