login

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

The description discloses the authentication method and returned tokens (access, refresh, token type), but lacks details on error handling, rate limits, token lifetimes, or security considerations. With no annotations provided, the description carries full burden and is minimally adequate.

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 concise with two sentences, front-loaded with the action verb 'authenticate'. No unnecessary words, every sentence contributes meaning.

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 return values (access token, refresh token, token type) partially, but does not explain token type or mention that this tool is typically the first step for authenticated requests. With no output schema, more detail 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 description coverage is 100%, and the description adds no extra meaning beyond what the schema already provides. It merely repeats the need for username and password, so baseline score of 3 is appropriate.

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 tool authenticates with username and password and returns tokens. It is specific and identifies the resource (authentication) and action (return tokens). However, it does not differentiate from sibling tools like 'auto_login' or 'refresh_token'.

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 usage for obtaining an access token for subsequent API requests, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like 'auto_login'.

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