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

No annotations are provided, so the description must carry the transparency burden. It usefully discloses that the result is scalar summary data rather than geometries or time series, but it does not state read-only semantics, data source, or freshness. For a simple profile endpoint this is acceptable but minimal.

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 one short sentence with the key distinguishing terms front-loaded and presented as a two-item list. There is no filler; the only minor cost is the slightly cryptic phrase 'dwelling-mix scalars.'

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 single-required-parameter lookup with an output schema, the description is nearly sufficient: it names the specific output metrics, which is what an agent needs to choose this endpoint. The output schema covers return shape. It does not address selection among adjacent development endpoints, but that gap is already reflected in the low usage-guideline score.

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 tool description does not explain the suburb_name parameter, its expected format, or how it maps to the returned metrics. The parameter name is self-evident, but the description adds no semantics beyond the schema.

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 identifies the data domain (dwelling mix) and the exact returned scalars: apartment share and average lot size. This distinguishes it from sibling development tools like density or zoning tools. It lacks a verb and reads as a noun phrase, but the purpose 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 statement of when to choose this over suburbs_development_all, density, supply, or other development siblings. An agent can only infer the intended use from the two metric names, so usage guidance is essentially absent.

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