auth_status

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

The description conveys the tool's core behavior: it returns a summary of logged-in accounts and pending sessions. Because no annotations are provided, the description carries the full burden, and it reasonably implies a read-only status operation. It doesn't detail potential side effects, but for an overview tool, no major mutation behavior is expected.

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 succinct sentence that immediately communicates the tool's purpose. It includes two key idea elements — logged-in accounts and pending login sessions — with no repetition or filler.

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, no-output-schema tool, the description is reasonably complete. It tells the agent what resource is being observed and what kind of state information will be surfaced. It does not describe the exact shape of the output, but for an 'overview' read operation this omission is minor.

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 no parameter documentation is needed. The description correctly focuses entirely on what the tool returns rather than arguing about inputs, which fits the baseline for parameterless tools.

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 indicates that this tool provides an overview of logged-in accounts and pending login sessions. It identifies the resource (authentication status) and implies a read/view action, which separates it from login-flow siblings like auth_start_qr_login and auth_poll_qr_login. However, it does not explicitly distinguish its behavior from accounts_list, which may overlap.

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 phrase 'Overview of logged-in accounts and pending login sessions' implies this should be used when the agent wants to check current authentication state. It does not explicitly specify when to choose this over accounts_list or the QR login flow tools, nor does it state any exclusions or conditions.

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