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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: results are limited to 'published' listings, coordinates are deliberately jittered (~100m) for landlord privacy, and exact addresses are shared only after contact with consent. That privacy caveat directly shapes how an agent should present results and is not derivable from any structured field.

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, each doing distinct work: purpose first, then the blocking prerequisite, then the output caveat. Nothing is repeated and the most important constraints are 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?

For a 14-parameter search tool with an output schema already covering return values, the description supplies exactly the missing pieces an agent needs: the mandatory country prerequisite and the jittered-coordinate privacy caveat. No call-critical information is absent.

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 high at 79%, so the schema already documents limit caps, rent/stay bounds, and the enum values. The description reinforces the required/conditional nature of country_type (ask the user or infer it) but adds no syntax or format detail for the location or filter parameters, so the baseline 3 applies.

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 names a specific verb and resource — 'Search published Flathive room/property listings' — plus the scoping dimensions ('by location and filters'). It is clearly distinct from a details-fetch tool, though it never names the sibling get_property_details explicitly, so an agent must infer the split.

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?

Strong prerequisite guidance: it states country_type is required and instructs the agent to ask the user or infer the country from a named suburb/city before calling. It does not state when to prefer this over get_property_details, leaving that transition to inference.

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