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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal that it returns exactly 10 suburbs and that it uses a similarity model, which is meaningful. However, it doesn't clarify input requirements, sort order, or any edge-case behavior, leaving some important gaps.

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 concise sentence with no filler. It front-loads the key outcome (top-10 similar suburbs) and names the underlying model. It could be slightly expanded to clarify the input role without losing conciseness.

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 one-parameter tool with an output schema, the description is minimally adequate but not complete. It doesn't explain how suburb_name is used or how this differs from comparable-suburb tools. The missing parameter semantics and usage guidance prevent it from being fully self-sufficient.

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 0%, and the description does not mention suburb_name at all. It does not add any meaning beyond the raw schema field name, and it fails to clarify that the provided suburb is the reference for similarity. The description needed to compensate for the bare schema and did not.

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 states a clear action (ranking) and resource (suburbs) and identifies the result count and model. It does not explicitly mention that it compares to a given suburb, but the name and schema imply it. This is more clear than vague, though it doesn't strongly distinguish from sibling tools like suburbs_market_comparable_suburbs.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention conditions, exclusions, or related tools such as suburbs_market_comparable_suburbs. The usage context is left entirely to inference.

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