bilibili_me

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description does add one piece of real context beyond them: it operates on the currently bound session and verifies login, implying it can fail when unauthenticated. It says nothing about what the returned profile contains.

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?

A single short sentence, front-loaded with the [账号] category tag, with no redundant restatement of the title. It is efficient, though bordering on under-specified for an auth-gated read.

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-param read tool with full annotation coverage, the description is close to adequate, but it leaves real ambiguity: how '本人的资料' differs from bilibili_user_info, and how this differs from bilibili_auth_status. With no output schema, a hint about the returned profile shape would also help.

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 are no semantics for the description to compensate for. Baseline 4 applies; nothing is missing or misleading on this dimension.

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?

States a specific verb phrase (核验登录 / 读取本人资料) on the 'self' resource scoped to the bound session, which implicitly separates it from bilibili_user_info. However, it never names the near-identical sibling bilibili_auth_status, so an agent must guess which one is the auth probe.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The phrase 使用当前已绑定会话 hints that no credentials are supplied, but nothing tells the agent whether to prefer this over bilibili_auth_status or bilibili_user_info.

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