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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive behavior, so the description need not restate safety. It adds useful context by enumerating the methodology topics covered and noting that the methodology page_url is included, which tells the agent this returns explanatory documentation rather than live figures.

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 definition is a single sentence with no filler and leads with the core purpose. The trailing list is dense but earns its place by scoping the methodology content, though the phrase 'with the methodology page_url' is slightly awkwardly attached.

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 zero-parameter documentation tool with an output schema, the description covers the main topics and notes the page_url. Combined with annotations and the output schema, an agent has enough to call it correctly; only an explicit usage cue would make it fully 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?

The tool has zero parameters, so the baseline is 4. No parameter semantics are needed or missing, and the description appropriately spends no space on input arguments.

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 this as a documentation/metadata tool: notes on how CrimeMapsUK builds its figures. It lists the covered topics (coverage, locations, rates, rankings, outcomes, citation), distinguishing it implicitly from the data-returning siblings area_rankings, area_summary, and postcode_summary. It does not explicitly contrast itself with those siblings, so a 4 rather than a 5.

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?

Usage is only implied: an agent can infer this is the tool to consult for methodology and definitions. There is no explicit when-to-use, when-not-to-use, or named alternative, nor any prerequisite such as calling it before interpreting sibling results.

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