Get a single listing

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

With no annotations, the description carries the full burden. It discloses the output contents (complete description, photos, floorplans, agency/agent contacts) and accepts input formats. However, it omits any discussion of error handling, rate limits, or what happens when a listing is unavailable or invalid, which are notable gaps for an unannotated tool.

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 two sentences, front-loaded with the primary action 'Fetch full detail' and immediately specifying the resource. It avoids fluff, making every word count while remaining concise and well-structured.

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 simple one-parameter fetch tool, the description adequately explains the input format and the key output components (photos, floorplans, contacts). However, it lacks details about potential error conditions or whether the listing must be currently active, which would round out the context.

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 provides a full description of the sole parameter (listing) with examples of URL and numeric ID, achieving 100% coverage. The tool description repeats the same information without adding new meaning, so it does not enhance the schema beyond what is already documented.

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 fetches full detail for one realestate.com.au listing, enumerating specific content like photos, floorplans, and contacts. This distinguishes it from sibling tools such as search_listings, which likely return multiple listings, by focusing on a single record.

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 implies usage when you have a specific listing URL or numeric ID, providing clear context for when to use this tool. However, it does not explicitly name alternatives or state when not to use it, though the single-listing focus inherently guides appropriate selection.

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