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

No annotations are provided, so the description carries the full burden. It signals a PRO/paid tier and the schema documents the subscriber token, but it does not disclose return limits, pagination, whether results are cached, or what 'full' means operationally.

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 single sentence is front-loaded with the resource and scope, with no wasted words. The 'PRO.' fragment is terse but effective as a tier signal.

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?

With no output schema and no annotations, the description should say more. It omits valid status values, return structure, how this differs from 'major_incidents', and any pagination or volume expectations.

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 coverage is 50%. The description adds useful semantics for 'status' by calling it an optional filter, and the access_token parameter is documented in the schema. However, the description does not list valid status values, leaving the filter domain ambiguous.

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 concrete resource and scope: 'Full NSW major incidents list.' However, 'PRO' is cryptic, and 'full' does not clearly differentiate this tool from the sibling 'major_incidents'; an agent cannot confidently tell which list tool to choose.

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?

It only notes that a status filter is optional. There is no guidance on when to use this tool versus 'major_incidents' or 'near_postcode', no prerequisites, and no exclusion criteria.

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