Upcoming scheduled rides

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description's bar is lower. Beyond that, it discloses nothing: not whether results are ordered by pickup time, whether past-but-unstarted rides appear, whether results are paginated or capped, or how empty results are signaled.

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?

A single five-word sentence with no filler, and the resource is front-loaded after the verb. It is efficient, though its brevity edges toward under-specification rather than crispness.

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 zero parameters, no output schema, and a read-only annotation, the definition is minimally adequate for an agent to call the tool. It leaves open what "later" covers and what the returned ride records contain, which matters since no output schema documents the return shape.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description adds nothing about filtering because no filtering is possible.

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?

"Lists rides booked for later" gives a specific verb (Lists) and a scoped resource (rides booked for later), which separates it in spirit from list_rides (existing/current rides) and schedule_ride (creating one). However, it never names those siblings, so the agent must infer the boundary between this and list_rides from the word "later" alone.

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?

There is no explicit when-to-use guidance, no exclusion, and no mention of the natural alternative list_rides or of cancel_scheduled_ride for follow-up actions. Usage is only implied by the tool name and the phrase "booked for later".

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