authenticate

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

With no annotations provided, the description carries the full burden. It discloses that the tool opens a browser window, navigates to a login page, waits for user credentials, saves session cookies to a file, and has a default timeout. This is substantial behavioral context beyond the schema.

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 three sentences: main action, process details, and cookie persistence/timeout. Every sentence adds value and is front-loaded with the primary purpose.

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 workflow (browser, navigation, wait, cookie save) and the default timeout. It lacks details on return values, error handling, or how to verify success, but the cookie-saving outcome is clear and the complexity is manageable.

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?

The schema only lists a timeout parameter with a default of 120, but no units. The description adds that the timeout is in seconds and explicitly states '120 seconds by default', providing meaning beyond the raw schema.

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 'Authenticate' and the target resource 'GUAP', and explains the browser automation process. It distinguishes itself from sibling data retrieval tools by being the authentication step.

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 that this tool should be run before subsequent requests, noting that cookies will be used automatically. However, it does not explicitly mention when to use vs alternatives like check_auth_status, nor does it state any exclusions.

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