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

With no annotations, the description carries the behavioral burden. It discloses that `total` is computed before `limit` so counts remain accurate when rows are capped, and that `verbose` includes full description text averaging 1.5 KB per listing. This adds meaningful context beyond the schema.

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 concise: a single sentence stating the purpose, followed by a short paragraph explaining `total`, `limit`, and `verbose`. It is front-loaded and every sentence adds value with no redundancy.

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 output schema covers return fields, and the description explains the key nuances of `total` and `verbose`. It lacks explicit alternative guidance, but for a straightforward listing tool with a well-defined output schema, the essential information is present. The missing usage alternatives are a gap but not critical.

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 schema already describes `limit` and `verbose` with defaults and behavior, including the `total` note. The description repeats this and adds only a trivial 'Raise limit for more listings'. For `suburb_name`, the description's 'in the suburb' is the only clarification, which is minimal. Overall, the description adds little beyond the schema.

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 returns current for-sale listings in a suburb with specific fields (address, price, beds/baths, coordinates). This distinguishes it from other suburbs_* tools like suburbs_market_stock_on_market (which gives counts) and suburbs_sales_recent (which gives recent sales, not for-sale listings).

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 gives parameter-level guidance (raise limit, set verbose) but does not explain when to choose this tool over alternatives. It doesn't mention scenarios where this is preferable to properties_context_nearby_for_sale or suburbs_sales_recent. No exclusions or alternative routing are provided.

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