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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds useful editorial context ('listed, never ranked; no one pays to be here' and data sourcing 'from its own site'), but says nothing about what happens with an empty query or how limit/default result sizing behaves.

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 dense sentence front-loads the directory's scope before the search mechanics, and the category enumeration is deferred to the schema rather than repeated. Some phrasing ('no one pays to be here') is marketing-tinged but does convey a useful non-commercial guarantee.

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?

With an output schema present, return-value explanation is unnecessary, and all four filters are at least touched on. The only real gap is default/limit behavior for an unconstrained call, which an agent may need to call it efficiently.

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 50%: query and category carry descriptions, island's enum is self-explaining, but limit has no description in either schema or description. The description links the params to search behavior ('Search by words, island or category') but adds no detail on limit defaults or maximum result counts.

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?

States a specific resource (a curated directory of 193 places) and the retrieval mechanism ('Search by words, island or category'), plus the exact domains covered (Kiawah, Seabrook, Johns Island, Wadmalaw, Charleston). It is unmistakably distinct from siblings like fees, flood_zone, estimate_range and true_cost.

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 names the three search axes (words, island, category), which implies how to invoke it, but gives no explicit when-to-use/when-not-to-use guidance relative to alternatives such as happenings or island_market, which an agent could plausibly confuse for local listings.

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