ride_login_import

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing beyond the one-line purpose. For a security-sensitive credential operation it doesn't say where tokens are stored, whether it overwrites existing sessions, what auth/permissions are required, or whether it has side effects. Only the bare 'import' concept is conveyed.

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?

The single sentence is front-loaded and free of padding, but it is arguably too terse for the operation it describes, leaving the reader under-informed rather than efficiently informed.

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?

No annotations, no output schema, and four undocumented parameters for a credential-import tool. The description supplies none of the surrounding context an agent needs, making it materially incomplete for the task.

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?

Four parameters at 0% schema description coverage, so the description is the only source of meaning and it provides none. 'token', 'access', 'refresh', and 'device' are left entirely undefined — no formats, no indication of which are required (all optional per schema), no explanation of how they relate.

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+resource ('import tokens') and scopes it to 'from browser', which does distinguish it somewhat from ride_login_send/verify/refresh. But 'tokens' is unexplained (auth tokens? access/refresh?) and it doesn't clarify what the import actually does or why an agent would pick it over ride_login_refresh. Purpose is implied rather than stated.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternatives like ride_login_refresh or ride_login_guided. The agent must infer the selection context entirely on its own.

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