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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully discloses that the tool returns both a suburb-level rollup and per-microburb shares, which is more than a bare purpose statement. However, it does not describe limitations, data availability, or how the shares are computed.

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 efficient sentence with no filler. It front-loads the core metric and immediately adds the useful 'suburb rollup plus per-microburb shares' distinction. Every piece contributes value.

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 simple one-parameter demographic tool with an output schema, the description gives enough context to understand the metric and output granularity. However, it lacks usage guidance relative to the many sibling tools, does not explain the 'microburb' terminology, and leaves the suburb_name parameter underspecified.

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 only parameter, suburb_name, has no schema description. The phrase 'suburb rollup' weakly suggests that suburb_name is a suburb, but the description does not explain the expected format, required structure, or how the parameter maps to the metric. This is a clear gap given the low schema coverage.

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 specific metric ('Share of residents attending Catholic / Independent schools') and resource ('suburb rollup'), which is clear and reasonably distinct from other suburb tools. It does not use an explicit verb like 'returns' or 'shows', but the noun phrase 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 on when to use this tool versus alternatives such as suburbs_demographics_all, suburbs_schools_all, or suburbs_schools_ranking. The description implies it reports private school attendance, but it does not state exclusions, prerequisites, or when a different sibling would be more appropriate.

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