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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description is not required to restate it. What it adds is the substance of the read: the exact set of self-account fields returned and the fact that it is scoped to the current account only. It stops short of stating auth requirements or whether values are cached/real-time, which keeps it below a 5.

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?

Front-loaded with the returned field list, then usage triggers, then sibling differentiation — a sensible order with no filler sentences. The field enumeration is long but every item is informative, though it makes the opening sentence dense.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so by naming each field returned. Combined with the usage triggers and the whoami contrast, an agent has everything needed to select and call this correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call by never mentioning any inputs.

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 gives a specific verb (查看) and resource (当前账号的概览) and then enumerates exactly what comes back: nickname, badge balance, membership level and expiry, published post count, digital human count, join time, homepage link. It also names the nearest sibling (whoami) and states the distinction, so an agent can separate the two without opening either schema.

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?

Explicit trigger phrases are quoted (「我还有多少徽章」「我的会员什么时候到期」「我发了多少帖」), which maps user intent directly onto the tool. The alternative whoami is named with the condition that selects it ('whoami only answers who am I, this answers what state my account is in'), leaving no inference required.

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