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

Goes well past the annotations (readOnly/idempotent/non-destructive are already supplied) by disclosing a hard cap of 8 rows, that filtered-out rows return in `ruledOut` with a reason, that `closed` flags permanently shut studios, and that pricing carries `pricingVerifiedAt` which is usually older than `lastVerified`. It also states that `doorsOpenState`/`doorsCloseAt` are computed in America/New_York and describe venue hours, not the class timetable – exactly the kind of non-obvious detail an agent would otherwise misread.

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?

Front-loaded with the subject, which is good, but it degrades into a dense backtick-heavy wall of run-on sentences mixing purpose, field glossary, filtering semantics and fallback behavior. The information mostly earns its place, but the structure makes it hard to scan for the operational facts.

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-shape burden and does a reasonable job: row cap, `ruledOut`, `closed`, `townScope.recognized`, `didYouMean`. Minor gap: only some row fields are named, so an agent can't fully anticipate the row shape, and the interaction between `town` and `query` is not spelled out.

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 the schema already defines all three parameters and the `access` enum values. The description still adds meaning: that the `access` filter is exclusive and produces `ruledOut` output, that `townScope` reports how the place argument was interpreted, and what happens when it isn't recognized (`rows` empty, `didYouMean` populated).

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?

Specific resource and scope: 'Verified East End places to train, 102 in all' followed by an enumeration of venue types (gyms, yoga, spin, courts, dance schools). It's clear what the tool returns, though it never distinguishes itself from the sibling `play_sport`, which plausibly overlaps on courts and sport.

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?

Gives concrete usage behavior for arguments ('With no argument nothing is looked up and the answer lists the kinds and towns covered'; the `access` argument filters to one kind) but offers no when-to-use versus when-not guidance and never routes the agent to or away from siblings.

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