get_listing

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

With no annotations, the description must disclose behavioral traits itself. It clearly states this is a read operation ('Fetch') and enumerates the return payload, but it does not disclose behavior on missing IDs, authentication requirements, or any response shape beyond field names. It is adequate but not rich.

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?

One front-loaded sentence with zero filler. It names the operation, the resource, the input mode, and the return fields efficiently.

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 single-parameter read tool with no output schema, the description is largely complete: it covers the operation, the identifying input, and the return contents. It could add error/not-found behavior or auth requirements, but those are minor gaps at this complexity level.

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 description coverage is 100% — the schema already defines id as 'Listing ID' and accepts string/number. The description only adds the qualifier 'numeric', which is slightly narrower than the schema but not significant. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 opens with a specific verb and object ('Fetch full details of a Sheypoor listing') and scopes it with 'by numeric ID'. The enumerated return fields (title, price, seller, images, etc.) make it distinct from sibling tools like get_listing_images (images only) and get_listing_from_url (URL-based lookup).

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 phrase 'by numeric ID' implies the precondition for calling this tool, but the description never states when to prefer get_listing_from_url or get_listing_images, nor when not to use this tool. Usage context is implied rather than explicit.

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