hemmabo_search_similar

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, establishing safe behavior. Description adds useful context: returns similar available properties with live pricing and excludes source property. No contradictions.

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 clear sentences with a bullet-like list of matching criteria. Front-loaded with purpose, no wasted words.

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?

Given no output schema, description states it returns 'a list of similar available properties with live pricing, excluding the source property.' Adequate for a search tool. Also covers when to use vs initial search. Slightly vague on output structure but overall 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 coverage is 100%, with detailed per-parameter descriptions including UUID format, date patterns, and guest count range. Description does not add per-parameter details but overall context (e.g., source property ID from hemmabo_search_properties) is already in schema. 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?

Description clearly states it finds vacation rental properties similar to a given property on specific dates. It explicitly says to use after hemmabo_search_properties, distinguishing it from sibling tools like hemmabo_search_properties (initial search) and hemmabo_compare_properties (likely comparison). Verb 'Find' and resource 'similar properties' are specific.

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?

Explicitly says 'Use this tool after the user has selected a property' and 'Do NOT use for the initial search; use hemmabo_search_properties instead.' Also lists matching criteria: same region, same property type, same or larger capacity. Clear when-to-use and alternatives.

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