login

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

The description discloses the browser login flow and config file saving, but does not mention side effects like overwriting existing credentials, required user interaction, or behavior on failure. No annotations exist to compensate.

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 that is front-loaded with the core purpose and mechanism. No redundant information; every word adds value.

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 simple parameter (optional boolean) and no output schema, the description adequately covers what the tool does. Could mention subsequent API key usage, but completeness is high for a login tool.

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 100%, so baseline is 3. The description adds context about the overall flow but does not elaborate on the 'force' parameter beyond the schema's own description.

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', the resource 'RunAPI', and the mechanism 'PKCE login flow'. It distinguishes from siblings (all unrelated to auth) and specifies the output location.

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 explicit guidance on when to use this tool versus alternatives. Sibling tools are unrelated to authentication, implying it's the primary auth tool, but no 'when-not' or 'if already authenticated' advice is given.

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