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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and 'Read-only' merely echoes them. The description does add genuine context beyond the structured fields: departure times are in Pacific time, prices are all-in USD per seat, and the returned set includes driver rating, trips, note, flexibility and cancellation policy.

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?

Purpose and id provenance are front-loaded, then the returned fields are enumerated in one dense sentence. The enumeration is long but justified because there is no output schema; nothing reads as filler.

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 thoroughly (route/stops, times, seats, price, driver info, note, flexibility, cancellation policy, booking link). Parameter origin, read-only nature, and timezone/currency units are all covered.

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% and the single parameter is documented there as 'The ride id.', so the schema does the heavy lifting. The description adds meaningful provenance beyond the schema by specifying the two places the id can be obtained, which prevents the agent from guessing.

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 and resource ('Public details of one Seat Sherpa ride by its id') and distinguishes itself from search_rides by naming it as the id source. An agent can tell it apart from list_service_areas, post_ride_link, and request_ride_link immediately.

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 tells the agent where the ride_id comes from ('from search_rides or a seatsherpa.app/ride link'), which is clear routing from the sibling tool. It does not state when not to use it or what to do if the id is unknown, so it stops short of explicit when/when-not guidance.

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