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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing beyond the implied read-only nature of "search." No mention of result limits, pagination, ranking, or whether unfiltered searches are allowed, all of which matter for a tool with zero required parameters.

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?

A single five-word sentence with zero padding, front-loaded with the verb. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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?

An output schema exists so return values need not be explained, but for an unannotated search tool with all-optional parameters and four siblings, the description omits everything an agent needs for correct routing and invocation. It is not complete enough given the tool's role.

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% and each of the three parameters has its own inline description with examples, so the schema does the heavy lifting. The tool description adds no parameter meaning beyond that, which is the baseline case for full coverage.

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?

It names a verb ("Search") and a resource ("NuVista Haven vacation rentals"), but this is close to a restatement of the title "Search Properties" with only the corpus brand swapped in. It gives no indication of what can be searched or how results differ from sibling tools like get_property_details.

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?

There is no guidance on when to use this tool versus check_availability, get_quote, or get_property_details, nor any prerequisite or exclusion stated. The agent must infer that this is the discovery entry point from the name alone.

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