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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, covering safety. The description adds real behavioral value beyond that: structural errors do not enter the ride or consume a step, while semantically poor but valid payloads do, and it notes the return contents. These are meaningful mechanics not derivable from annotations.

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?

Three tight sentences, front-loaded with the core action then the validation/step rule then the return shape. No filler, and each sentence carries distinct 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 complex multi-variant action tool with an output schema, the description covers the essentials: validation strictness, step consumption, and the fact that a next observation is returned. It slightly overlaps the output schema by restating returns, but is complete enough for correct invocation.

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 50%; the action parameter is richly documented via nested variant descriptions, while runId has no description anywhere. The description clarifies that action variants are constrained by the latest observation and that validation is strict, adding meaning over the raw schema, but leaves runId semantics implicit. Baseline 3 fits.

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 ("Submit one strictly validated action") and resource ("for the ride identified by runId"), which is unambiguous about what the tool does. It does not explicitly contrast itself with siblings like start_ride or list_rides, but the purpose is clear enough to distinguish operationally.

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?

"Use a payload variant allowed by the latest observation" gives procedural guidance on how to select an action, but offers no when-to-use framing relative to siblings (e.g., after start_ride, before get_scorecard). Usage is implied rather than stated, so a 3 is appropriate.

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