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

The description adds value beyond annotations by disclosing that AI virtual-staging is 'always AI-disclosed', that contact details are omitted, and that only active listings are returned. These are specific behavioral traits not covered by readOnlyHint/openWorldHint/destructiveHint. No contradiction with annotations.

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 concise and front-loaded, with two sentences: the first lists return contents efficiently, the second gives usage guidance. Every phrase adds value (e.g., 'always AI-disclosed', 'Contact details omitted'), with no filler or redundancy.

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?

Despite having an output schema, the description enriches context by enumerating the returned fields and specifying omissions and constraints (active listing, AI disclosure, contact details omitted). For a single-parameter read tool, this provides sufficient context for an agent to invoke it correctly and anticipate results.

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 coverage is 100% as the only parameter, property_id, is already described as 'Evlek listing UUID'. The description adds no further parameter meaning beyond repeating 'by UUID'. Baseline for high coverage is 3, and there is no extra semantic detail.

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 'Return' and the resource 'a 360° profile of one active Evlek listing by UUID', listing concrete fields. It distinguishes from discovery tools by noting 'Don't use for: discovery' and explicitly names search_listings as the alternative. The title also reinforces the tool's role for a single listing by UUID.

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 explicit usage conditions: 'Use when: a UUID is already known' and 'Don't use for: discovery — use search_listings first.' This gives clear context for when to select this tool over the sibling search_listings and implies when not to use it. The UUID-specific nature also hints at differentiation from get_listing_by_number, though not named.

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