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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that listings are 'live' and enumerates return fields, but since a rich output schema exists, that enumeration is largely redundant; nothing is said about result ordering, empty-result behavior, or result caps beyond the schema's limit.

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 sentences, front-loaded with the core action and scope, followed by the payoff. No filler, no restatement of the title.

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 12-parameter, all-optional search tool with full schema coverage, annotations, and an output schema, the description covers what the tool does and what comes back. A minor gap remains around result limits/defaults and how to chain into the sibling report tools, which the schema does not answer.

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%, with per-parameter descriptions for area, bedrooms encoding (0=studio, 4=four or more), rent bounds, and filter flags. The description adds no parameter-level meaning beyond the schema, 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?

States a specific verb and resource ('Find apartments for rent') with an explicit scope ('New York City', 'right now'). It is clearly distinguishable from siblings like get_apartment (single listing), nearby_apartments (proximity), and the report tools. An agent can tell this is the primary discovery/search entry point.

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 verb 'Find' and the 'right now' live-listings framing, but the description never says when to prefer this over nearby_apartments, nor does it state that callers should follow up with get_apartment for a single listing or building_report for history. No exclusions or prerequisites are given.

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