ride_track

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

With no annotations provided, the description carries the full behavioral burden. "Snapshot" hints at a read operation but the description says nothing about polling behavior, whether it blocks, what timeout does, or what happens with follow. Significant gaps for a tool with zero annotation coverage.

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?

Extremely short, which is fine structurally, but the brevity is under-specification rather than genuine conciseness. A single sentence that doesn't earn its place by conveying any actionable information.

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?

For a 3-parameter tool with no annotations, no output schema, and 0% schema coverage, the description is completely inadequate. Nothing an agent needs to correctly invoke this tool is present.

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?

Three parameters (token, follow, timeout) at 0% schema description coverage and no enum values. The description adds zero meaning: "follow" and "timeout" are particularly ambiguous without explanation, and this is the one place description could compensate. It does not.

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?

"Active ride snapshot" is a noun phrase that loosely implies retrieving ride status but lacks a clear verb and doesn't distinguish itself from siblings like ride_status or ride_boarded. An agent cannot confidently tell what this tool does differently from ride_status based on the description 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?

No when-to-use context, no exclusions, and no mention of how it differs from the very similar sibling ride_status. The agent is left to guess whether to call this or ride_status.

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