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

Annotations already establish the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is additive. It does add two useful behavioral facts: results are confined to 'their own market' and it 'returns names only, not listings', which with no output schema is a meaningful disclosure about return content.

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 short sentences, zero filler, with the core lookup purpose front-loaded and the scope constraint immediately after. Nothing could be removed without losing 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?

For a small read-only lookup tool with no output schema, the description covers purpose, market scope, and result type (names, not listings). Only the limit/pagination behavior and how query matching works are unaddressed, which is a minor gap.

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 only 50% (query is documented, limit is not), so the description should compensate, yet it says nothing about either parameter — no matching semantics for query, no cap/default behavior for limit. The 'in their own market' phrasing hints no market parameter exists but adds no real semantics.

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 verb+resource ('look up neighborhood names and ids') and scopes it to what the connected renter can add to their alert search, which separates it from the plain list_neighborhoods sibling without naming it. The distinction is inferable but not explicit.

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?

Usage is implied by the alert-search framing, but there is no explicit when-to-use statement and no guidance on why an agent would pick this over list_neighborhoods or get_search_preferences. The reader must infer the routing decision.

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