bilibili_auth_status

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

Annotations only tell the agent the call is read-only; the description adds two traits that matter and are not in structured data: credentials are never returned, and verify=true causes real-time validation against Bilibili (implying latency/network dependency). It stops short of saying what happens when verification fails.

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?

One compact sentence that front-loads the return contract and then the parameter behavior; every clause adds information and nothing repeats the name or schema.

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?

With no output schema, the description says what is excluded but not what the returned session status actually contains (e.g., logged-in flag, username, expiry), leaving the agent to discover the shape at runtime. Adequate for a one-param read tool, but with a clear gap.

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?

Schema coverage is 0%, so the description must carry the single parameter, and it does: verify=true means live validation, with the default of false implied. Lacking only a note on failure/timeout behavior for the verify path.

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 a specific resource (本地会话状态和账号) and explicitly bounds the return payload by excluding Cookie/key, which sharpens what the tool is. It does not, however, differentiate from the sibling bilibili_me, which an agent could easily confuse it with.

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 clause about verify=true implies when to pay the cost of a live check, but there is no explicit when-to-use/when-not guidance and no routing away from bilibili_me or bilibili_user_info. Usage is inferable rather than stated.

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