ride_balance

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 and delivers nothing: no statement that this is a read-only operation, no authentication requirements for the token, no info about the returned balance or currency. The description is two words and discloses no behavior at all.

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 short and front-loaded, but the brevity comes from under-specification rather than economy. Two words with no verb or object communicate almost nothing about the operation.

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?

With no annotations, no output schema, an undocumented token parameter, and a dense field of 50+ sibling tools, the definition is far too thin for an agent to invoke this tool correctly or route to 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?

The single 'token' parameter has 0% schema description coverage, and the description adds no meaning, not even that it is an authentication credential. The tool is not parameter-free, so the baseline-4 shortcut does not apply and the description fails to compensate.

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 'Wallet balance' simply restates the tool name ride_balance as a noun phrase, with no verb and no scope. It does not distinguish this tool from closely related siblings such as ride_wallets or ride_debts, so an agent cannot tell them apart from the description alone.

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?

There is no guidance whatsoever on when to use this tool, when not to, or which alternative to prefer. With ride_wallets, ride_debts, and ride_profile in the sibling list, the absence of routing guidance is a serious gap.

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