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

With no annotations, the description carries the full behavioral burden and does disclose two useful traits: no cost and no API key required. However, it omits read-only confirmation, rate limits, error behavior, and any pagination or response-format context.

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?

Two short, front-loaded fragments state the core purpose first and access conditions second. It is efficient, though the extreme brevity contributes to some under-specification rather than pure conciseness.

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 read tool, the description gives the essential return shape ('one listing in full') and access conditions. Missing information includes where listing_id comes from and what the response object looks like, but the tool's low complexity keeps this from being severely incomplete.

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 required parameter listing_id has no description in the schema. The description implies an identifier is needed to retrieve 'one listing,' but adds no format, source, or constraint details for listing_id.

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?

States a clear verb+resource scope: retrieve one listing in full, which distinguishes it from search_listings by returning a single complete listing. It does not explicitly name the sibling or specify what 'full' omits, but the purpose is readily inferable.

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?

Provides no when-to-use guidance or alternative routing. 'Free, no key' indicates access conditions but does not explain when this tool should be chosen over search_listings or other listing-related siblings.

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