Trip details

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds a useful field inventory but nothing about permissions, rate limits, or failure modes (e.g. what happens for an unknown or cancelled trip id).

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?

One sentence, front-loaded with the resource and then the payload, with zero preamble. The field enumeration is dense but each item earns its place by telling the agent what will come back.

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?

A single-parameter read tool whose safety profile is fully covered by annotations and whose return shape is covered by an output schema. The description supplies the field summary on top, leaving little an agent would still need to know before calling it.

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% with a single required 'id' whose schema description already states it is a 36-char trip id from uber_trips. The prose adds no format, validation, or lookup semantics beyond that, so the baseline of 3 applies.

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 names a specific resource (a single past or upcoming trip) and enumerates the exact fields returned — status, fare, product, driver, pickup/drop-off, times, distance, duration, surge, route map. The phrase 'One ... trip' implicitly contrasts with the list-oriented sibling uber_trips, but the contrast is never stated outright.

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?

No explicit when-to-use or when-not-to-use guidance is given in the description. The only routing signal, that an id comes 'from uber_trips', lives in the schema's parameter description rather than the tool text. The 'past or upcoming' phrasing implies the lookup use case without stating it.

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