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

With no annotations, the description carries the full burden of disclosing behavior. It only lists output categories and says nothing about side effects, permissions, rate limits, or whether the operation is read-only. For a data retrieval tool, this is a significant omission.

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?

The description is extremely short, which is concise, but it is a fragment rather than a well-formed sentence. It lacks a verb and front-loads a list of terms without context. While brief, it is not structured in a way that aids comprehension.

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 the tool returns a rich lifestyle summary (implied by output schema) and there are many related lifestyle tools, this description is grossly incomplete. It does not explain what 'POI category breakdown' means, how terrain scalars are quantified, or what the flags represent. The agent would need to inspect the output schema to understand the tool, but that is not sufficient for deciding when to call it.

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?

The single parameter suburb_name has zero schema description coverage and the description never mentions it. The agent receives no information about expected format, valid values, or how the parameter relates to the returned data. The description adds no semantic value beyond the parameter name.

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?

The description is a noun phrase listing content items ('POI category breakdown, terrain scalars, nearest train/shop and beach/hospital flags') without a clear verb or resource. It does not state what action the tool performs or what it returns, making it difficult for an agent to distinguish it from other lifestyle tools like suburbs_lifestyle_livability or suburbs_lifestyle_pois.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., suburbs_lifestyle_cbd, suburbs_lifestyle_landmarks). The description offers no conditions, alternatives, or exclusions, leaving the agent to guess which lifestyle summary is appropriate.

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