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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description goes well beyond them. It discloses the classification taxonomy (permanently closed / temporarily closed / never-existed), that each row carries the confirming date and reporter, and the exact failure shape when `townScope.recognized` is false (empty rows plus `didYouMean`).

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 two operating modes are front-loaded before the classification detail, and nearly every clause carries information. It is a dense single block, though, and the taxonomy plus `townScope` explanation could be tightened without losing meaning.

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, the description takes on the burden of explaining return structure and does so: row classes, dates, reporters, and the unrecognized-place response with `didYouMean`. Nothing an agent needs to interpret the result or call it correctly appears to be missing.

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 100%, so `name`, `town`, and `since` are already documented, including the 'omit to list' behavior. The description reinforces the dual-mode meaning of `name` but adds no new syntax or semantics for `town` or `since`, so it sits at the baseline for a fully described schema.

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 specific resource (verified East End venue closures) and explicitly splits the tool into two modes: a single-venue verdict when `name` is supplied, and a list of recent confirmed closures otherwise. It even clarifies that the verdict covers venues the guide lists as operating, which separates it from a plain closure feed.

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 when-to-use rule is clear and stated up front: pass `name` for a single-venue verdict, omit it to list recent closures. It does not name alternatives (e.g. whats_open_now or search_places) or state exclusions, so an agent must infer the boundary with those siblings.

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