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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is fully covered. The description adds the scope (single listing) and the specific facts returned, which is useful but does not disclose any additional behavioral traits like error handling or data consistency. Given the rich annotations, a 3 is appropriate.

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, front-loaded sentence that states the core purpose and scope with zero wasted words. It is appropriately concise and well-structured.

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, single-parameter tool with annotations covering safety and an output schema present, the description covers the essential purpose, scope, and content. It lacks explicit guidance on when to prefer this over siblings, but that is partially covered in usage guidelines. Overall it is adequately complete for an agent to call it 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?

The input schema has full coverage (100%) of the single parameter, describing it as a listing title with partial matching allowed. The description does not add any further parameter semantics beyond what the schema already documents, so it meets the baseline but does not enhance it.

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 verb ('get' implied) and resource ('listing details') with a clear scope ('ONE listing already in play') and enumerates the returned facts (amenities, description, capacity, base price). It distinguishes from sibling tools like search_listings (search vs. existing) and check_availability_and_price (facts vs. availability/pricing).

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 'already in play' implies this is for a listing already identified, not for discovery, which is useful context. However, it does not explicitly name alternative tools or state when not to use it, leaving the agent to infer from sibling names. It gives clear context for use but lacks explicit exclusions.

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