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

No annotations are provided, so the description must disclose behavioral traits, but it only lists output content. It does not mention behavior when no active ride exists, authentication requirements, or that it is a read-only operation beyond the verb 'Get'. This is a significant gap for a tool that may return an error in edge cases.

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, well-structured sentence that front-loads the main purpose and lists specific return elements. Every word earns its place, with no fluff or redundancy.

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?

The description covers the happy path (what data is returned) but lacks details on error handling or the no-active-ride scenario. Given no output schema or annotations, the description is expected to provide this context, making it minimally adequate but not fully complete.

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 has zero parameters, and the schema inherently covers 100% of them. Per the rubric, a zero-parameter tool gets a baseline of 4; the description adds no parameter info but none is needed.

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 clearly states the tool's function: 'Get the status of the user's current active ride' with specific detail about included data (driver details, ETA, ride status). This distinctly separates it from sibling tools like get_ride_history (past rides) and book_ride.

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?

The phrase 'current active ride' implies the appropriate context (when the user has an ongoing ride) and implicitly rules out use for past or future rides. However, it does not explicitly state when to avoid using it or name alternative tools, so it lacks exclusions.

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