get_item

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

With no annotations, the description does some work by listing the fields returned (description, price, photos, attributes, seller, availability) and implying a read-only lookup. However, it does not state error behavior for invalid identifiers, whether data is cached or live, or any authentication/visibility constraints.

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 the key action first, followed by accepted identifier formats and return fields. No filler; the enumeration of return fields is compact and informative.

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 one-parameter getter with no output schema, the description provides the identifier flexibility and a summary of returned fields, which covers what an agent needs to call it correctly. Minor gaps remain around error handling and access conditions.

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 single 'item' parameter has no description in the schema. The description compensates well by specifying that the identifier may be an id, slug, or URL, which is essential for correct invocation.

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 states a specific retrieval action ('Details of one listing') and names the resource plus acceptable identifiers (id, slug, URL). It clearly distinguishes from a list/search tool by emphasizing 'one listing', though it does not explicitly name a sibling like search or similar_items.

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?

Usage is only implied: the agent can infer this tool is for fetching a single listing's details when the identifier is known. There is no explicit guidance on when to prefer it over search, search_filters, or similar_items, and no exclusions are stated.

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