ride_login_guided

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. 'Browser-guided' hints that a browser session or user interaction is involved, but nothing is said about how the flow is driven, what the helper does, how timeout is enforced, or what happens on failure.

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?

Three words with zero padding is technically concise and front-loaded, but the brevity here is under-specification rather than efficiency. There is no wasted sentence because there is essentially no content.

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 an authentication flow with three undocumented parameters, no annotations, and no output schema, the description is far too thin. An agent cannot determine required inputs, flow behavior, or return values from what is given.

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 no parameters at all. The three parameters (token, helper, timeout) are entirely undocumented, so an agent has no idea what values to supply.

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 phrase 'Browser-guided login' names a verb (login) and a modality (browser-guided), which is enough to know it authenticates a user. However, it does not distinguish itself from the many sibling login tools (ride_login_send, ride_login_verify, ride_login_import, ride_login_refresh), so it is vague about which login path this is.

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 statement of when to use this tool versus the four other ride_login_* siblings, nor any prerequisite or ordering information. An agent must guess whether this replaces or follows ride_login_send/verify.

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