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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only states that the tool provides a bundle of count and list, but gives no information about output structure, pagination, data freshness, or any side effects. The term 'bundle' is a minimal hint but insufficient for an agent to anticipate 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 extremely concise (six words), which is positive, but it is so terse it reads like a fragment rather than a structured explanation. It is not front-loaded with key details because there is no detail to front-load; it sacrifices informativeness for brevity.

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 description is inadequate for a tool with an output schema and many siblings. It does not explain what the combined response looks like, how count and list are interrelated, or when to prefer this over the separate tools. An agent cannot determine whether this tool suits a given task without additional investigation.

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 input schema has a single required parameter 'suburb_name' with no description, and the tool description does not mention it at all. With 0% schema description coverage, the description needed to clarify the parameter's meaning and format but fails to do so, providing no added value beyond the schema's type.

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 'DA count + DA list — bundle' clearly indicates the tool returns both development application count and list data, distinguishing it from the separate count and list siblings. It names the specific resource (DA) and implies a suburb context via the parameter. However, it does not explicitly state the resource is a suburb, so it's not fully explicit.

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 the separate suburbs_development_da_count or suburbs_development_da_list tools. The description does not state that this bundle is for getting both at once or any trade-offs, leaving the agent to infer usage 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.