get_listing_details

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

No annotations are present, so the description carries the full burden. It only says 'get full details' but does not disclose any behavior such as error handling, required permissions, read-only nature, or potential side effects. The name implies a read operation, but beyond that, transparency is minimal.

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 purpose, and includes a simple 'Args' section. Every word earns its place with no redundancy or filler.

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 get tool, the description is sufficient: it explains what the tool does, what the parameter is, and where to obtain it. The presence of an output schema covers return values. It lacks only extra context like error behavior, but overall it is complete enough for straightforward use.

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 input schema only defines listing_id as a string with no explanation. The description adds essential meaning by identifying it as a RentCast listing ID and noting it comes from search_sale_listings, which is valuable context 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 fetches full details for a specific sale listing by its RentCast ID. This distinguishes it from sibling tools like search_sale_listings (which lists) and get_property_record (which returns property data), giving a specific verb+resource+scope.

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 mentions the listing_id is returned by search_sale_listings, which implies this tool is used after search and when full details are needed. However, it does not explicitly exclude other scenarios or mention alternatives, so it stops short of full guidance.

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