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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses important behavioral traits: road results are a published pattern, not a live incident feed, and are computed against America/New_York; every figure carries a source; `sourceCaveat` marks figures not published at the linked source; and `townScope.recognized: false` explains an empty rows array plus possible `didYouMean` matches.

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 core purpose is front-loaded, but the description is a dense, run-on paragraph that packs fares, surcharges, timezone logic, source caveats, and place-resolution edge cases together. Much of the detail is useful, but the structure makes it harder to scan than a shorter or segmented definition would be.

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 burden of explaining return concepts and does so thoroughly: it names the fare and schedule fields, describes `roadConditionsNow`, explains `sourceCaveat`, and specifies the `townScope` failure behavior. For a complex read-only guide with only two optional parameters, this is sufficient context to call and interpret the tool.

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 baseline is 3, but the description adds real meaning about how `to` affects the result: it reports which Jitney stops serve that destination and the relevant drive-time row with typical and summer minutes. It also explains how the place argument is interpreted via `townScope`, though `mode` itself is mostly left to the 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 clearly states a specific resource and activity: reaching the East End and moving around by named transport modes, with fares and road-window answers. It is distinct from siblings such as parking_permit_rules or where_to_stay, but it does not explicitly compare itself to any sibling, so it falls short of 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 implied for trip-planning and local transport questions, and the description explains that omitting `to` gives the whole picture while supplying `to` enriches results with Jitney stops and drive times. However, it gives no explicit when-not-to-use guidance or named alternatives among the many sibling tools.

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