ride_login_refresh

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: no auth requirements, no token lifetime or invalidation semantics, no statement of whether the old token is destroyed, and no response behavior. For an authentication-related mutation this is a severe gap.

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 extremely short, but this is under-specification rather than conciseness. A three-word phrase cannot be front-loaded meaningfully because there is no substantive content to order.

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 two-parameter authentication tool with no annotations, no output schema, and no parameter documentation, the description leaves an agent unable to invoke it correctly. Nothing explains the flow context or what a successful refresh yields.

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?

Both parameters ('token', 'refresh') have 0% schema description coverage, and the description adds no meaning at all — it does not say what 'token' should contain, whether 'refresh' is a refresh token, or which are required (schema reports 0 required).

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 verb ('Refresh') and a resource ('ride token'), which is more than a tautology and hints at renewing an existing credential rather than creating one (distinguishing it loosely from ride_login_send/verify). However, it never clarifies what token is being refreshed or that this belongs to the ride login flow, so the differentiation from the many ride_login_* siblings is only implied.

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 call this versus ride_login_send, ride_login_verify, or ride_login_import. There is no mention of expiry conditions, prerequisites, or the alternative paths an agent should consider when a token fails.

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