Eva Login

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly discloses the main side effect—discarding the cached session—and that the login is forced. However, it does not mention whether credentials are required, whether this invalidates other active state, or what failure or error behavior might look like.

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 a single, efficient sentence with no filler. The core action and side effect are front-loaded, and 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?

For a zero-parameter tool with an output schema and no nested inputs, the description is largely complete: it identifies the action and primary side effect. It could add context about when to choose this tool, such as stale session detection, but nothing essential for invoking it correctly is missing.

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?

The tool has zero parameters, so there is no parameter meaning for the description to add. With schema coverage at 100% and an empty schema, the baseline of 4 for parameterless tools is appropriate, and the description correctly adds no parameter-specific detail.

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's action: force a fresh login and discard the cached session. It is specific about the resource ('login') and the behavior, distinguishing it from the sibling data-retrieval tools rather than merely repeating the title.

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 this should be used when a fresh login or session reset is needed, but it does not explicitly state when to use it versus alternatives or whether it should precede other eva_* calls. There is no exclusion or alternative routing, only an implied usage context.

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