furunavi_auth_login

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

No annotations provided; description covers opening a browser, user interaction, and saving session. Mentions headless and timeout parameters implicitly, but doesn't disclose behavior for already authenticated states or error conditions.

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?

Single sentence clearly communicates the tool's action and expected user involvement. No redundant information; front-loaded with key action.

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?

Given the interactive login complexity and no output schema, the description lacks details on prerequisites, the login UI, cancellation, error handling, or post-login state. Leaves significant gaps for effective agent use.

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%. The description does not explain the parameters individually. It implies headless=false but doesn't describe timeoutSeconds or its effect. Parameter meaning relies on user inference.

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 clearly states it opens a browser, logs into Furunavi via user interaction, and saves a session. It distinguishes from sibling tools like furunavi_auth_status (status check) and furunavi_auth_clear (clear session).

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 implies usage as an initial login step but lacks explicit guidance on when to use or not use it. No mention of prerequisites or alternatives like furunavi_auth_status to check if already logged in.

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