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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's added note that 'each stay can belong to multiple lifestyle categories' provides useful result-set semantics that help interpret duplicate appearances. This goes beyond structured fields and does not contradict any annotation.

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 two sentences, front-loaded with the primary function and quickly adds the multi-category nuance. Every word contributes meaning, with no filler or redundant information.

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 is a straightforward read-only list filter. The combination of schema (with parameter details), annotations (read-only, safe), and a clear description fully covers usage. No output schema is needed for this simple list operation, and the description provides sufficient context for an agent to invoke 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?

Both parameters (lifestyle and limit) have detailed schema descriptions with 100% coverage. The schema explains the partial-match behavior and default limit, while the tool description only repeats examples and adds no new parameter semantics. The baseline of 3 is appropriate since the schema carries the full load.

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 uses the specific verb 'Returns' and identifies the resource as 'stays from the NomadStays database', filtered by 'lifestyle/genre category'. It includes concrete examples that clarify the domain and clearly distinguishes it from sibling tools like getStaysByAmenities or getStaysByBudget, which filter by different criteria.

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 establishes this tool as the lifestyle-based filter for stays, and the parameter description directs users to the getAllLifestyles tool for valid categories. It does not explicitly state when not to use it or name alternative filtering tools, but the context is clear enough for an agent to select it appropriately.

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