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 only states the data content and does not mention whether the operation is read-only, how data is aggregated, or any caveats about the breakdown. This is not contradictory, but it is largely transparent about behavior.

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 phrase with no redundant words or filler. It front-loads the core meaning, though it could be slightly more informative without becoming verbose.

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?

This is a simple one-parameter tool with an output schema, so the description plus schema may be enough for a basic call. However, missing usage guidance and behavioral context means an agent has limited information for choosing it confidently among many similar demographics and income-related sibling tools.

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 parameter, suburb_name, with no description, and schema description coverage is 0%. The description never mentions suburb_name or explains how it relates to the income breakdown, so it adds no semantic value beyond the bare parameter name.

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 identifies the resource: household income breakdown by bracket. It distinguishes the tool from the sibling suburbs_demographics_income_map by emphasizing 'by bracket' rather than a map, though it lacks an explicit verb such as 'returns' or 'gets'.

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?

No guidance is provided about when to use this tool versus alternatives like suburbs_demographics_all, suburbs_demographics_income_map, or other demographics tools. There are no when-to-use or when-not-to-use instructions, leaving the agent to infer context from the name alone.

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