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

The description does not disclose any behavioral traits beyond the basic 'recent' and 'in the suburb' scope. Since no annotations are provided, the description carries the full burden. It fails to mention whether results are limited by date range, pagination, or any ordering; it also does not hint at the output schema (though output schema exists). It adds minimal context beyond what a name implies.

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 sentence with no fluff. It front-loads the core purpose ('Recent development applications') and scopes it to the suburb. It is appropriately sized for a simple tool.

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?

Given that the output schema exists, it may cover return values, but the description still lacks contextual details like the time window for 'recent', whether it returns a list or summaries, and any prerequisites (e.g., knowing the suburb name). The sibling tools are extensive, and without specifics, an agent might confuse this with similar DA tools. It is minimally complete.

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%, meaning the schema provides no descriptions for the parameter 'suburb_name'. The description mentions 'in the suburb' which contextualizes the parameter, but it does not specify the expected format (e.g., exact name, case sensitivity, or valid values). Since there is only one required parameter, the description should at least confirm it is a suburb name string, which it does implicitly but not with enough detail.

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 'Recent development applications lodged in the suburb' clearly states the tool returns recent DA listings for a suburb, with a specific noun phrase. It differentiates from adjacent tools like 'suburbs_development_da_count' (which likely returns a count) but not explicitly from 'suburbs_development_applications' which may be a near-synonym. The verb is implied rather than explicit, which slightly reduces clarity.

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 provides a clear context: it is for retrieving recent development applications for a given suburb. However, there is no explicit guidance on when to use this tool versus alternatives like 'suburbs_development_applications' or 'suburbs_development_da_count'. The sibling list contains many development tools, but no when-not or alternative naming is given. This is minimum viable.

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