risha_refresh_context

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

The description mentions 'Login again' implying re-authentication, but it does not disclose whether this invalidates previous sessions, if it is destructive, or what the output or side effects are. With no annotations, this lack of behavioral detail is a significant gap.

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, focused sentence that front-loads the core action ('Login again and refresh startup context') followed by details. It is appropriately sized 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?

For a zero-parameter tool with no output schema, the description adequately covers what the tool does. However, it is incomplete in that it does not explain what the result is (does it return the refreshed data?) or any behavioral traits, which limits full understanding.

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 zero parameters, and the description accurately reflects that no parameters are needed by stating it refreshes all context. It adds meaning by explaining why no parameters are required—because it refreshes tied state.

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 that the tool logs in again and refreshes startup context including user, capabilities, and credit balance. It distinguishes itself from sibling tools like risha_login or risha_startup_state by combining both actions, though the exact boundary between these tools could be more explicit.

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?

No guidance is provided on when to use this tool versus alternatives such as risha_login or risha_startup_state. The description does not mention prerequisites, scenarios, or exclusions.

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