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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does reveal that the output is human-readable plain-English text, which is a meaningful behavioral trait, but it does not mention what livability dimensions are included, whether the narrative is derived from other endpoints, or any limitations such as coverage or availability. The disclosure is too thin for a tool with zero annotations.

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 a single, compact phrase with no filler or repetition. It front-loads the key information about the output format and the subject, and every word contributes meaning. It is appropriately short for a simple one-parameter tool, though it could have been structured as a full sentence.

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 has only one param and an output schema exists, the description does not need to enumerate return values. It tells the agent the basic purpose and output style, making it minimally viable. However, it lacks any guidance on what 'livability dimensions' are covered, how the narrative relates to the other lifestyle endpoints, or any constraints on the suburb_name input, leaving noticeable gaps for tool selection and correct invocation.

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 schema has one required parameter, suburb_name, with 0% schema description coverage, so the description must compensate. The phrase 'for the suburb' merely restates the parameter name and adds no value about accepted formats, valid suburb identifiers, case sensitivity, or how to obtain a valid name. The parameter is self-explanatory by name, but the description does not enrich it.

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 clearly communicates that the tool produces plain-English narrative text broken down by livability dimension for a suburb. It is specific about the resource (suburb) and the output format (one sentence per dimension), which distinguishes it from numeric or map-based sibling tools like suburbs_lifestyle_livability or suburbs_lifestyle_livability_map. It lacks an explicit verb like 'returns' or 'generates', but the intent is unambiguous.

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?

There is no guidance about when to use this tool versus siblings such as suburbs_lifestyle_summary, suburbs_lifestyle_livability, or suburbs_lifestyle_pois. The description implies it is for narrative livability output, but it never states a preferred use case, exclusions, or alternatives, leaving selection entirely to the agent's inference.

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