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 behavioral context by revealing the hierarchical nature (a hub containing child locations and listed communities) and that slugs must be sourced from greystar_locations. It does not discuss pagination or depth limits of the hub, so it falls short of a 5.

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, both front-loaded and free of padding: the first defines the resource and its contents, the second handles disambiguation. Every clause earns its place.

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?

An output schema exists, so return-shape detail is unnecessary. With readOnly/openWorld annotations covering the safety profile and 100% schema coverage on params, the definition is essentially complete; only the recursive depth of the hub (how far child locations extend) is left implicit.

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%, so the baseline is 3, and the schema already documents each slug. The description adds real value beyond the schema by stating where the slugs originate (greystar_locations) and framing state/city/neighborhood as a locational hub hierarchy, which informs how the three params compose.

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 ('Fetch') and resource ('Greystar state, city, or neighborhood rental hub') and enumerates the payload ('child locations, listed communities, and FAQs'). It also names the sibling tools it is not, so an agent can distinguish it without opening any 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?

Gives an explicit prerequisite ('slugs must come from greystar_locations') and explicitly routes to three alternatives with the condition for each: greystar_property for one community, greystar_markets for market options, greystar_search to find rentals. Nothing is left to inference.

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