bilibili_live_room_info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only a hint that live status is included in the response; it says nothing about auth requirements, error behavior for invalid/nonexistent room IDs, or response shape.

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 with the resource front-loaded and zero filler. It is efficient, though its brevity comes at the cost of the missing guidance noted in other dimensions.

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 one-parameter read tool with no output schema, the description is minimally adequate: it tells the agent the tool returns room info plus live status. It falls short by not explaining the sole parameter's format or how it differs from the live_rooms listing endpoint.

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 description coverage is 0%, and the single parameter room_id is documented nowhere. The description does not clarify its format (numeric ID vs. short ID), valid ranges, or where an agent can obtain a room_id, which matters on Bilibili where short IDs are common.

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 names a specific verb and resource ("读取直播间信息和直播状态" – read live-room info and live status), which is clear about what it returns. It does not explicitly distinguish itself from close siblings such as bilibili_live_rooms (a listing tool) or bilibili_live_playurl, so sibling differentiation is left to inference.

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 statement of when to use this tool versus bilibili_live_rooms or bilibili_live_playurl, and no prerequisites or exclusions. An agent must infer from the name alone that this fetches a single room's metadata rather than a room list or stream URL.

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