ride_wallets

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

No annotations are provided, so the description carries the entire behavioral burden, and it discloses nothing: not whether this is a read or write operation, whether authentication/token scopes are required, what data is returned, or whether it mutates state.

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?

Two words are technically brief, but this is under-specification rather than conciseness — there is no useful content to front-load or trim. Nothing earns its place because nothing informative was said.

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 tool with no annotations, no output schema, and an undocumented parameter, the description is completely inadequate. An agent could not reliably decide when or how to invoke this tool based on the provided information.

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 single parameter 'token' has 0% schema description coverage, and the description does not mention it at all. The agent gets no explanation of what the token should be (session token? wallet token? identifier of a specific wallet?).

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?

"Payment wallets" is a noun fragment that essentially restates the tool name ride_wallets rather than stating a verb and resource. It gives no indication of the operation (list wallets? fetch balances? manage stored payment methods?) so an agent cannot distinguish it from siblings like ride_balance or ride_debts.

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 description provides no guidance on when to use this tool, no prerequisites, and no mention of alternatives. With 40+ siblings in the ride_* family, the absence of any routing signal leaves the agent with nothing to reason from.

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