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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context on top: fares are current and vary by prepaid vs. on-board payment, Cross Sound adds a fuel surcharge, road conditions are computed against America/New_York, and crucially 'There is no live incident feed behind this: it is the published pattern, not what the road is doing this minute.' That is exactly the limit an agent needs to avoid over-claiming.

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 resource list, but the whole thing is a single dense paragraph of roughly 250 words with redundancy ('so you can tell someone when to leave instead of guessing') and stacked parentheticals. Every claim is relevant, yet the wall-of-text form makes it slower to parse than it needs to 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 return-value burden and does so: sourceCaveat handling, roadConditionsNow contents (next window start, all three windows with days/hours), and the per-destination stop/drive-time rows. Combined with annotations covering the safety profile, an agent has everything needed to call and interpret this correctly.

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 baseline is 3; the description earns the extra point by explaining what passing `to` actually changes in the response (which Jitney stops serve it, the drive-time row, typical AND summer minutes) and by re-stating the `car-free` intent behind the enum. It goes beyond field labels without fully specifying the output shape.

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?

States a specific verb+resource with unusual precision: 'How to get to the East End and around it,' then enumerates the exact operators and data served (Jitney, LIRR, ferries, road conditions). No sibling tool covers transport, and the description makes that scope unmistakable from the first clause.

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 explicit trigger conditions — 'any getting-there, how-long, how-much or when-should-I-leave question, and for without a car' — plus the mode/`to` routing rules. No when-not guidance or named alternative is needed since no sibling competes for this intent, but the absence of any exclusion keeps it short of a 5.

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