domain_search_listings

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the geographic scope ('Australian'), but omits behavioral facts an agent needs: that an api_key credential is required, whether results are paginated or capped, and how openWorld querying behaves if all filters are omitted.

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?

One efficient, front-loaded sentence with no filler, so it is concise; but the brevity is under-specification rather than density, and the single sentence carries almost no operational information.

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 10-parameter search tool with no output schema and near-zero schema coverage, the description should at minimum explain the credential requirement, filter semantics, and result behaviour. None of that is present, so the definition is inadequate to call the tool reliably.

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 10% — just listingType ('Sale or Rent') — across 10 parameters including state, suburb, postcode, price and bedroom ranges, api_key and pageSize. The description contributes no parameter meaning whatsoever, leaving nearly every field's format, optionality semantics and interaction undocumented.

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 states a specific verb and resource ('Search Australian property listings on Domain'), which is unambiguous and tells an agent exactly what kind of data comes back. It does not, however, distinguish this from sibling tools like domain_get_property or domain_suburb_stats, which also touch Domain property 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?

There is no guidance on when to use this versus domain_get_property or domain_suburb_stats, no mention that filters can be combined, and no note about pagination or what to do when no filters are supplied (all 10 parameters are optional). Usage is only implied by the word 'Search'.

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