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

Annotations already indicate a non-read-only, non-idempotent operation. The description adds context by naming the exact API endpoint and revealing the side effect of storing the Bearer token in the session, which is valuable beyond the annotations. It does not contradict any annotation.

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?

A single concise sentence that front-loads the action and includes the endpoint and purpose. No filler or redundancy, every word contributes.

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?

With only two well-documented parameters and an output schema available, the description sufficiently covers the tool's operation. It could be improved by explicitly stating that this is a prerequisite for authenticated endpoints, but 'for later tools' already conveys that. Overall it is complete for a simple 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 coverage is 100% and each parameter already has a clear description (email with format and fallback, password as account password). The description merely repeats 'using email and password' without adding new semantics, so baseline 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 states a specific action (log in) with a specific resource (Botsify Authorization API POST /v1/login) and explains the outcome (store Bearer token for later tools). It clearly distinguishes this tool from siblings like create-oauth-token or select-bot by focusing on email/password session login.

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 phrase 'store the Bearer token for later tools in this session' implies this should be invoked before other authenticated tools. However, it does not explicitly mention when not to use it or compare with alternatives such as create-oauth-token, so it lacks explicit exclusions.

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