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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. The description adds the hierarchical scope (state/city/neighborhood hub) but does not disclose auth needs, rate limits, or any nuance beyond what annotations and schema provide.

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?

Front-loads the verb and resource, then lists return contents compactly, closing with the slug prerequisite. Efficient, though the return enumeration is somewhat dense and partly redundant with the output schema.

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?

Given an output schema exists, the return details are supplementary; the description still supplies the essential prerequisite and the hierarchical scope. Complete enough to invoke correctly, with only cross-sibling ambiguity remaining.

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 state, city, and neighborhood slugs and the city dependency for neighborhood. The description only re-states 'slugs must come from greystar_locations', adding nothing beyond the schema. 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 clear verb+resource: 'Get one Greystar state, city, or neighborhood rental hub', and enumerates the returned fields (title, editorial blocks, child locations, communities, FAQs). It references greystar_locations and greystar_property, giving partial sibling routing, though it doesn't contrast with greystar_markets or greystar_search directly.

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?

'Slugs must come from greystar_locations' is a concrete prerequisite and points to a related tool. However, there is no guidance on when to choose this hierarchical hub over siblings like greystar_property or greystar_search, leaving usage selection implicit.

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