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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is low. The description still adds genuine context: the per-listing payload fields (address, weekly rent, beds/baths, coordinates, off_market) and the temporal 'live right now' freshness claim, which matters because there is no output 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?

Two short sentences, front-loaded with the resource and scope, then the payload and paging note. No filler, every clause earns its place.

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?

With no output schema, listing the returned fields and the off_market flag is the right compensation, and safety is covered by annotations. It stops short of spelling out the paging/filter behavior it defers to the for-sale tool, which leaves a small gap for an agent that must page results.

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 75% and limit/verbose/off_market are already well documented in the schema. The description's only added semantic is that paging and filters mirror the for-sale tool, which is a useful pointer but not new parameter meaning, and suburb_name remains undocumented in both places.

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+resource ('Rental listings live right now in the suburb') and enumerates the returned fields, so the agent knows exactly what it fetches. It implicitly separates itself from the for-sale sibling via 'Rental' and 'Same paging and filters as for-sale', but never names that sibling explicitly.

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?

Usage is only implied by 'live right now in the suburb'; there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., suburbs_listings_for_sale, suburbs_finder_search). The 'same paging and filters as for-sale' note gestures at a related tool but gives no routing rule.

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