ride_carpool_reject

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

No annotations are provided, so the description carries the full burden. '(dry-run)' hints that no state change occurs, but it is vague and arguably contradictory for a mutation-named tool; there is no mention of auth needs (the 'token' param), what 'confirm' does, or what side effects occur on a real rejection.

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?

It is a single short phrase, so there is no padding. However, the brevity is under-specification rather than efficiency: the one parenthetical present introduces ambiguity instead of useful signal.

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?

This is a state-changing tool with no annotations, no output schema, and three undocumented parameters, so the description should do much more. It omits permissions, confirmation flow, and the meaning of the dry-run flag, leaving the agent unable to call it confidently.

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% across three parameters (token, confirm, offer_id), and the description explains none of them. In particular the relationship between 'confirm' and the '(dry-run)' claim is left completely unaddressed, so the agent must guess how to drive a real rejection.

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?

It names a specific verb and resource ('Reject carpool offer'), so the basic action is discernible. But the '(dry-run)' parenthetical creates ambiguity about whether the offer is actually rejected, and it does not distinguish itself from the sibling ride_carpool_dismiss, which reads like an overlapping alternative.

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 on when to reject versus dismiss or accept an offer, and no stated preconditions. The agent must infer the selection criteria entirely from the tool name.

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