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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'recover any active session,' which implies a potential state-changing action, but does not clarify side effects, reversibility, or whether the operation is safe. It also does not specify if the tool is read-only or modifies session data. This vagueness is insufficient for an agent to understand the impact of calling it.

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 sentence, concise and front-loaded with the core purpose. It avoids unnecessary detail and gets to the point quickly. However, it is somewhat terse and could benefit from a bit more specificity about session recovery, but it remains efficient.

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 the tool has no parameters and an output schema exists (though its content is unknown), the description should clarify the tool's role and behavior enough for an agent to call it correctly. It covers the main functions but leaves ambiguity about what 'recover' entails and how it fits with sibling tools. The description is adequate but not fully complete for a tool that might alter session state.

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 nothing to document beyond the schema. The description does not need to add parameter semantics. The baseline of 4 is appropriate because no parameter information is required.

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 a specific purpose: showing authentication state, recovering active sessions, and suggesting next steps. It uses a verb ('Show') and a resource ('authentication state'), and the session recovery aspect adds specificity. However, it does not explicitly differentiate from sibling tools, which are numerous and could overlap (e.g., arcade_session, arcade_state).

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 provides no guidance on when to use this tool versus its siblings. It does not mention any alternative tools or conditions for choosing this one. The intended context is only implied by the purpose, not stated explicitly, so an agent has no clear direction on when to invoke it over others.

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