login

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

Discloses local callback URL, credential storage path and permissions (mode 600), and process application. Without annotations, it covers key behavioral aspects well, though doesn't mention idempotency or re-login behavior.

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 paragraphs with relevant details, but includes slightly verbose phrasing like 'Starts a local callback...' could be streamlined. Generally acceptable length.

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?

Does not describe return value or output schema, despite the tool having one. No error handling or prerequisite details (e.g., Supabase config). For a simple auth tool with one param, it lacks completeness.

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?

Only parameter `timeout_sec` is not explained in the description; schema shows only a title and default. With 0% schema description coverage, the description fails to add meaning beyond the default value.

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?

Clearly states it opens a Google login page and saves tokens, with specific verb ('open', 'save') and resource ('browser Google login page', 'tokens for this machine'). Distinguishes from unrelated sibling tools like convert_pdf.

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?

Advises running once instead of manual token pasting, mentions a CLI alternative, and notes Supabase redirect requirement. No explicit when-not-to-use or alternative authentication methods, but sufficient for basic use.

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