zhihu_check_login

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

The description discloses the return payload (logged_in and username), adding behavioral detail. The readOnlyHint annotation already covers safety, so the explanation of return values supplements it without contradiction.

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?

Single sentence with front-loaded verb and resource, zero filler. Every word adds meaning and the return values are mentioned compactly.

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, a read-only annotation, and the mention of return fields, the description fully covers the tool's needs. No output schema is present, but the description explicitly lists the expected return values.

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?

No parameters exist, so the baseline is 4. The description appropriately omits parameter details since there are none to document.

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?

Uses specific verb '检查当前知乎登录状态' (check current Zhihu login status) and explicitly mentions returns (logged_in and username). Clearly distinguishes from sibling zhihu_login, which presumably performs login.

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?

Provides clear context that this is a status-checking tool, implying it should be used to verify login before operations. No explicit alternatives or when-not-to-use guidance, but the purpose is self-evident and reading-oriented.

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