auth_login

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

No annotations are provided, so the description carries the full burden. It discloses key side effects: returns JWT access and refresh tokens, and stores them in session config for all subsequent requests. It also discloses the precedence condition (STORNO_TOKEN). It doesn't discuss failure behavior, rate limits, or what happens on invalid credentials, which prevents a 5.

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?

Two sentences with zero padding. First sentence states verb, resource, mechanism, and side effect. Second sentence states the usage precondition. Every word earns its place.

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?

For an auth tool with 2 simple parameters and no output schema, the description adequately covers purpose, side effects, and usage ordering. It could mention failure behaviors or password security best practice, but for its complexity this is reasonably complete.

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%, so the schema already documents both email (with email format) and password clearly. The description adds token/session context but doesn't add syntax or security guidance beyond the schema. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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?

Description states the specific verb 'Authenticate' with the Storno.ro API using email/password, clearly explains the auth flow (JWT tokens, session storage). Distinguishes itself from auth_refresh and other auth_* siblings by its explicit role in establishing initial session.

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 explicitly states the precondition: 'Must be called before any other tool if STORNO_TOKEN is not set.' This gives clear conditional guidance on when to use this tool versus relying on a pre-existing token, effectively covering the when-to and when-not-to basis.

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