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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network behavior are covered. The description adds scope (nationwide default) and return shape (communities with matching unit counts, units, filter counts), but the return shape is duplicated by the output schema and no auth, rate-limit, or pagination behavior is disclosed beyond the schema.

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 search action and ending with the location-prerequisite routing. Some content (filter list, sort options, return fields) duplicates the schema, which adds a little redundancy for an otherwise tight description.

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 all-optional params, an output schema covering return values, and annotations covering safety, the description supplies what remains: what is searched, the default scope, sort options, and where to get location slugs. It stops short only on disambiguating from other greystar search/detail tools.

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%, so the schema already documents page, per_page, sort, and the filter arrays including allowed values. The description only restates the same filter dimensions and sort options, adding no syntax or format detail beyond the schema.

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 (Search) and resource (apartment units on greystar.com), names the scope (one location, nationwide by default), and enumerates the filter dimensions. An agent can immediately tell this is the unit-inventory search rather than the site's generic greystar_search or a property detail tool.

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?

Explicitly routes the agent to the sibling greystar_unit_locations for the location argument and states the default behavior (nationwide). It gives clear context for invocation but does not state when to prefer a different tool, e.g. greystar_property or greystar_search.

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