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

Annotations only provide readOnlyHint and openWorldHint. The description adds meaningful behavioral detail: partial rent-bedroom coverage, the requirement to report it as approximate using rentBedroomCoveragePct and rentBedroomNote, and the building-level unavailability. No annotation contradiction.

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 sentences: the first front-loads the core return content, the second explains conditional behavior, and the third adds a caveat. No filler or repetition of schema details.

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?

There is no output schema, so the description carries the return-shape burden; it lists the headline metrics, the property-class mix, and the conditional breakdowns. It also includes reporting instructions and a limitation. Nothing essential for invoking the tool is missing.

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%, so the baseline is 3. The description adds value beyond the schema by clarifying that propertyClass breakdowns apply to communities and by flagging the per-building rent limitation, which helps an agent choose valid parameter values.

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 identifies a specific resource ('one community or area slug') and enumerates the headline stats returned, making the tool's purpose unmistakable. It is clear enough to be distinguished from building-specific siblings, but it never explicitly names an alternative tool such as get_building_stats.

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 conveys that the tool is for community/area slugs and warns that per-bedroom rent is not available for a single building, which implies limits. However, it does not explicitly state when to prefer get_location_stats over siblings like get_building_stats or get_market_overview, so routing is left to inference.

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