risha_login

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

The description mentions caching the JWT for the session, which is a useful behavioral trait. However, without annotations, it does not disclose potential side effects, idempotency, or failure modes (e.g., if credentials are invalid).

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, clear sentence that front-loads the key action and outcome, with no wasted words.

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?

Given zero parameters and no output schema, the description is fairly complete. It explains what the tool does and the result (cached JWT). A minor gap is that it doesn't mention what happens if the login fails or whether the JWT is automatically refreshed.

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 input schema has no parameters, but the description adds meaning by specifying that the tool uses RISHA_EMAIL and RISHA_PASSWORD (likely environment variables). This compensates for the lack of parameters.

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 it logs in to Risha and caches the JWT. It is distinct from sibling tools like risha_call or risha_generate_image, which are not login-related.

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 it should be used before other tools that require authentication (due to caching JWT), but does not explicitly state when to use it or when not to use alternatives. No guidance on prerequisites beyond environment variables.

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