site_login_status

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context by specifying the scope ('current Chrome Profile') and explicitly stating no platform task is executed, which reinforces the read-only nature without contradicting annotations.

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, front-loaded sentence with no redundant content. Every word adds meaning, and it is appropriately sized for a simple check tool.

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?

The tool is simple with one parameter and an output schema, so the description need not detail return values. It covers the essential purpose and platforms, but could add a small note about typical usage before platform tasks to fully contextualize its role among the sibling tools.

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?

There is one parameter with a well-defined enum, but schema property description coverage is 0%. The description lists the platforms in prose, partially compensating for the missing parameter description; however, it does not explicitly link the 'platform' parameter to the listed sites, relying on inference from the enum and the $defs description.

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 uses a specific verb ('Check whether') and clear resource ('current Chrome Profile logged in to Zhihu, Xiaohongshu, X, or Reddit'). It distinguishes itself from sibling platform task tools (e.g., zhihu_search, x_post) by explicitly stating 'without executing a platform task.'

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 'without executing a platform task' implies using this tool as a preflight check before platform operations. It names the relevant platforms and signals a non-invasive context, but it does not explicitly name alternative tools or provide exclusion criteria.

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