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

No annotations are provided, so the description carries the full burden. It states 'Get public details', which suggests a read-only, non-destructive operation. However, it does not explicitly confirm idempotency, rate limits, or authorization requirements, leaving some ambiguity.

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 that effectively communicates the core purpose. It is concise but might be overly terse; however, for a simple tool with one parameter, this level of conciseness is appropriate and does not waste words.

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 the low complexity (one parameter, no output schema), the description provides basic information. However, it omits details about what 'public details' include (e.g., title, price, description), and does not reference sibling tools or output expectations, leaving some gaps.

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?

With 0% schema description coverage, the description must explain the parameter. It merely says 'by its id' without clarifying what the id represents (e.g., listing ID number, text identifier) or its format. This adds little beyond the schema's type and minLength.

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', the resource 'listing', and the scope 'public details', with a specific identifier 'by its id'. This distinguishes it from siblings like 'search_listings' (which searches) and 'get_resale_price' (which gets a specific price).

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 that the tool is used when you have a listing id, but does not explicitly state when to use it versus the siblings. No exclusions or alternatives are mentioned, leaving the agent to infer usage context from the tool names.

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