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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the outputs in a brief list, but does not mention any data source, calculation methodology, potential limitations (e.g., data vintage, approximation for people per km²), or whether the counts refer to dwelling and resident counts. It does clarify the output fields to some extent, but the description is too thin to be considered transparent.

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 sentence that is concise and front-loads the key metric (dwellings and people per km²). It does not waste words)Skip? Actually, it's brief but informative in terms of listing output components. However, it could be slightly more structured with a period or bullet points for clarity. Overall, for a one-line description, it's appropriately short.

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?

The tool is relatively simple (one parameter, no nested objects) and has an output schema, which typically cover return values. The description covers the main output fields. However, given that there are no annotations and the parameter is undocumented, the description could have added usage context like 'Use this to get a quick density snapshot for a suburb' or mentioned how it relates to sibling tools. It's slightly below average completeness because it leaves out why an agent would need these specific fields.

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 a single required parameter 'suburb_name' with no description, and the schema description coverage is 0%. The tool description does not mention the parameter at all, so it provides no additional meaning beyond the parameter's name. For a parameter that is just a string, it's critical to state that it expects a suburb name, which the schema already implies, but also any format specifics (e.g., exact casing, region qualifiers) are missing.

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 that the tool provides dwellings and people per km² plus land area and counts, so the core purpose is reasonably clear. However, it doesn't explicitly mention what the parameter is (suburb_name) or what the output format looks like, and doesn't differentiate from many other suburbs_* tools at a glance. It's better than a tautology but still leaves some ambiguity.

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 gives no guidance on when to use this tool versus the many siblings such as suburbs_development_all or suburbs_demographics_population_history. It doesn't state a use case, exclusions, or prerequisites. The agent would have to infer that it's specifically about density metrics.

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