zhiqi_subscriptions

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

With no annotations, the description carries the transparency burden and does add useful context by requiring a locally configured userToken and limiting use to a specific human-login channel. It does not disclose output shape, pagination, or potential side effects, though '查看' implies a read operation.

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 one compact sentence with the core purpose front-loaded, followed by two essential constraints. There is no filler, repetition, or unnecessary detail.

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, read-only subscription lookup, the description covers the key invocation requirements: channel restriction and token setup. It could further describe the expected result list or ordering, but the tool's simplicity keeps the gap small.

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 is empty and has zero parameters, so there is no parameter meaning for the description to clarify; the rubric sets a baseline of 4 for 0-parameter tools. The userToken is correctly framed as local configuration rather than a schema parameter.

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 states '查看我的帖子订阅' (view my post subscriptions), giving a specific verb and resource, and clearly implies a read-only listing. It does not explicitly differentiate sibling tools like zhiqi_subscribe or zhiqi_unsubscribe, so it loses the top point.

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 concrete invocation context: '仅人类登录态通道 A' and '需要本地配置 userToken' tell the agent about prerequisites and channel restrictions. However, it does not state when to prefer this tool over siblings or offer any when-not-to-use guidance; usage is mostly implied by the name and verb.

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