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

With no annotations and no output schema, the description carries the full burden and mostly succeeds: it discloses the hardcoded geography and inventory scope, the freshness claim ("currently has available"), and enumerates every returned field. What it omits is result-size behavior — "every property" plus no parameters implies an unfiltered, potentially large result set, but pagination, truncation or ordering are never mentioned.

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 in a sensible order: what the tool returns, what each record contains, then what to do with the identifier. The field enumeration is long but earns its place because there is no output schema to document the shape.

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 parameterless list tool with no annotations and no output schema, the description covers scope, record shape, and next-step routing — enough for an agent to call it correctly. The remaining gap is expectation-setting about result volume and ordering, which matters for a query that returns an entire inventory.

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 tool accepts zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. It could have strengthened the point by explicitly stating that no filtering arguments exist, but the schema is unambiguous.

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?

Specific verb ("List") plus a precisely scoped resource: every available property for one named agency across two named geographies, restricted to offices/homes for rent or sale. It also implicitly distinguishes itself from get_listing (detail) and request_viewing (action) by naming them as downstream consumers.

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 final sentence gives an explicit workflow: take a listing_id from these results and feed it to get_listing or request_viewing, which routes the agent correctly among the three siblings. It stops short of stating exclusions, e.g. that there is no way to filter by district, price or deal type, which would be the key 'when not to use' caveat for a zero-parameter search tool.

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