auth_login

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

With no annotations, the description adds behavioral context about browser interaction for SSO/Playwright, but does not mention that this is a state-changing action (side effects like session creation) or potential errors. Moderately transparent.

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?

One dense sentence covers key information without redundancy. However, it could be structured more clearly (e.g., bullet points) for easier parsing, but remains concise.

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?

Adequately describes the main behavior and parameter usage context, but lacks details on return values, error conditions, or prerequisites. Given no output schema, more completeness would be beneficial.

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 covers all parameters with descriptions. The description adds value by specifying which parameters are needed for which authentication type (e.g., password only for JWT/Basic). Enhances semantic understanding beyond 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?

Clearly states it logs into an internal system and distinguishes different authentication methods (JWT/Basic, SSO, Playwright). Differentiates from sibling tools like auth_logout and auth_status.

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?

Implies usage context by describing different login flows depending on the system, but does not explicitly state when not to use this tool (e.g., if already logged in). Could be clearer about prerequisites.

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