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

With no annotations, the description carries the full burden and does disclose one real behavioral trait: results are capped at 100. It does not say whether that cap truncates silently, whether results are ordered, or what the PRO/subscriber requirement means operationally beyond the access_token note in the schema.

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?

Two compact fragments with the resource and cap front-loaded and zero filler. The unexplained 'PRO.' prefix is the only piece of text that doesn't clearly earn its place.

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 zero-required-parameter read tool this covers the basics, but with no annotations, no output schema, and an unexplained 100-result cap, an agent still lacks enough to predict truncation behavior or the shape of returned incidents.

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%: access_token is documented in the schema, while 'keyword' has no schema description. The description only adds that the keyword filter is optional; it doesn't say what fields the keyword matches against or how matching works, so it only partially compensates for the coverage gap.

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?

States the resource ('Emergency Victoria incidents') with a result cap and an optional filter, so the agent knows it retrieves a bounded incident list. It doesn't distinguish itself from the sibling 'incidents' tool, and the 'PRO' marker is never explained, so sibling differentiation is left implicit.

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?

'PRO' hints at a subscription gate but there is no explicit when-to-use guidance and no mention of when to prefer 'incidents' or 'near_postcode'. The agent must infer the selection logic from the sibling names alone.

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