getListingDetails

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

With no annotations, the description carries the burden. It discloses the tool's scope (domains) and included data, but omits behavioral aspects like request handling, error behavior, authentication, or how optional flags affect results. Since it is a read operation, the impact is moderate but still incomplete.

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 a single sentence, front-loaded with the main purpose. The parenthetical domain list adds practical specificity without unnecessary length, and every word contributes.

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?

Given four parameters, no output schema, and no annotations, the description is too sparse. It fails to describe the effect of optional flags, the return format, or any caveats, leaving significant gaps for an agent to invoke the tool correctly.

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 0%, and the description does not explain any of the four parameters. The words 'images' and 'seller info' loosely relate to the boolean flags, but no explicit linkage or meaning is provided, leaving the agent without enough guidance to set includeImages or includeSellerInfo correctly.

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 verb 'Get' and resource 'detailed information about a specific OLX listing', enumerates supported domains, and lists included content (description, seller info, images). The phrase 'specific listing' distinguishes it from the sibling tool 'searchListings'.

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?

It clearly implies use when a specific listing's details are needed, contrasting with search. However, it does not explicitly mention when not to use it or reference the alternative 'searchListings', so no explicit exclusions are provided.

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