Record Login Flow (Level 3)

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

Beyond annotations (openWorldHint, destructiveHint), the description details that it opens a browser, injects an action recorder, waits for manual login completion, records steps to config, and notes security (password/OTP never recorded). This adds significant behavioral context.

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 description is well-structured with a clear first paragraph stating purpose, a security note, a bulleted 'When to use' section, and an Args list. It is front-loaded and every sentence adds value without repetition.

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?

The description covers the core functionality, security, and usage scenarios but lacks explanation of the 'Level 3' concept and does not address error handling or cancellation behavior. However, given the tool's complexity and existence of an output schema, it is fairly complete.

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 coverage is 0%, but the description provides brief yet clear explanations for both parameters: account_id is 'the account id to use' and provider is 'Override the provider. Defaults to the account's provider.' This compensates for the lack of schema descriptions.

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 the verb 'Record' and resource 'login flow for future automatic replay'. It distinguishes itself from siblings like gv_sign_in (which replays) and gv_set_credentials (which stores actual credentials) by emphasizing the recording and teaching aspect.

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 'When to use' section provides explicit scenarios: complex login flows, sites where login form is hard to describe, and when you want to teach once then automate. It implicitly contrasts with simpler methods like login_steps and mentions future gv_sign_in calls will replay the steps.

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