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

The annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: results distinguish permanently closed, temporarily closed, and never-existed, and each record carries a confirmation date and reporter. It also states that a named lookup returns a verdict either way, even for venues the guide still lists as operating.

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 trigger conditions and the name/omit behavior are front-loaded and every clause is functional. It runs long and carries a slightly promotional framing ('the one thing a model cannot know'), but the concrete Bay Burger/Cyril's Fish House examples justify the hallucination-risk warning.

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 carries the return-value burden and does so: it describes verdict semantics, the three closure categories, and the confirmation/reporter metadata. Nothing an agent needs to decide whether to call it or how to interpret a result is 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 already 100%, so the baseline is 3, but the description adds real meaning for `name` (pass it for a single-venue verdict; omit it to list recent closures) and explains that the verdict is returned even for apparently-open venues. It says nothing extra about `town` or `since`, which is the only 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?

The description names a specific resource and scope ('Verified East End closures') and a second capability ('is-it-still-open check'), both matching the title. It distinguishes itself from siblings by explicitly contrasting with search_places and by handling venue-status questions that no other listed tool covers.

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 gives two explicit trigger conditions — (a) any question about whether a place is open or when it closed, and (b) before recommending a venue from the model's own knowledge — and names the alternative (search_places) that applies otherwise. Nothing is left to inference.

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