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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the hierarchical 'parent for nested ones' trait, which is useful, but the slug/URL return details largely restate the output schema rather than adding new behavioral context.

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 tight clauses with the core purpose front-loaded and the query hint second. No filler; the only mild redundancy is enumerating return fields that the output schema also carries.

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 read-only, single-optional-param list tool with an output schema and covering annotations, the description supplies enough to call it correctly. The missing piece is explicit routing versus sibling location 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% and the single optional param is documented as text matched against the slug (e.g. austin). 'Use query to narrow by text' confirms the intent but adds no syntax or matching semantics beyond the schema, so the baseline of 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?

Specific verb 'List' plus a precisely scoped resource: locations that the greystar_units search accepts, from nationwide US down to neighborhoods. It anchors itself to a named sibling (greystar_units) so an agent can distinguish it from greystar_locations/location without opening a schema.

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 'Use query to narrow by text' line implies a usage context, and the resource scope implies it feeds greystar_units. However it never states when to choose this over the nearby greystar_locations/greystar_location siblings, nor any exclusions, so guidance is only implied.

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