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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is its disclosure of data scope: MLS sales since 2021 and a median price/sqft computed only where five or more sales allow, and the 'facts about places only' framing that rules out subjective content. That is genuinely useful beyond the structured fields.

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?

Scope is front-loaded in the first sentence, but the second sentence is a long, dense enumeration of return fields that partially duplicates the output schema. It is serviceable rather than tight.

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, the description need not explain return structure, and it is complete enough to call the tool: one required enum parameter, three valid islands, and the level of detail the agent should expect. It never says how Johns Island differs in content from the Kiawah/Seabrook branch, which is a minor omission.

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% and the single enum parameter's meaning (including the Johns Island/Kiawah River note) is fully documented in the schema. The description adds no format, syntax, or selection detail beyond it, so the baseline 3 applies.

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 title and description make clear this is a full listing of neighborhoods for one of three named islands, with per-island content enumerated (type, area, regime manager, MLS history). It is distinguishable from the singular sibling get_neighborhood by scope, though that contrast is never stated in words.

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 explicit when-to-use guidance and no mention of alternatives such as get_neighborhood for a single neighborhood or island_market for market-level data. The only implied usage is 'you want everything on an island,' which an agent must infer from 'Every neighborhood on...'.

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