ride_block

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

No annotations are provided, so the description carries the full behavioral burden. It hints at non-mutating behavior via 'dry-run', which is useful, but doesn't explain what state is simulated, whether the dry-run has side effects, what auth ('token') is required, or what a successful result looks like.

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 terse, front-loaded but under-specified. Six-word descriptions aren't concise if they leave core questions unanswered; brevity here reads as incompleteness rather than discipline.

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?

No output schema, no annotations, 0% schema coverage, and a one-line description. An agent has essentially no information to correctly invoke a 3-parameter, potentially mutating tool.

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 description coverage is 0%, and the description mentions none of the three parameters ('token', 'confirm', 'ride_id'). For a tool with a 'confirm' boolean that presumably toggles between dry-run and real execution, omitting all parameter semantics is a serious gap.

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 'Block driver (dry-run)' names a verb and an object, but is ambiguous about what 'block' means in this ride-hailing context (block a driver account? an action?) and fails to distinguish itself from any of the many ride_* siblings. The parenthetical '(dry-run)' is the only concrete information, and it implies the operation doesn't actually mutate anything.

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 guidance whatsoever about when to use this tool, when not to, or which alternatives (if any) apply. Given the ~50 sibling ride_* tools, an agent has no way to determine the intended trigger conditions from the description alone.

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