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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by noting it returns non-activated properties, which is a distinctive behavior not obvious from annotations or schema. It also mentions the geographic scope and filter categories.

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 only two sentences, front-loading the core purpose and then summarizing filters and return type. Every sentence adds value with no fluff 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?

The tool has 7 parameters and no output schema, but the description covers the essential return type (property listings including non-activated) and key filters. It does not describe pagination or exact listing fields, but for a search tool with well-documented schema, it is sufficiently complete.

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 100%, so all parameters have meaningful descriptions. The tool description maps some filters (price range, bedrooms, superhost, World Cup city) to parameters but does not provide additional meaning beyond the schema, such as format or edge cases. Baseline 3 is appropriate.

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 tool searches 'lilo's market discovery for vacation rental properties' with specific filters (price range, bedrooms, superhost, World Cup 2026 host cities) and returns listings including non-activated properties. This distinguishes it from sibling search tools like search_vacation_rentals and search_world_cup_rentals by focusing on market discovery for research.

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 the tool is for market research by highlighting 'non-activated properties for market research' and 'market discovery'. It gives clear context on when to use it (for research on vacation rental market) but does not explicitly state when not to use it or provide alternative tool names.

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