bilibili_danmaku

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds that only public XML danmaku are read and that output is capped at `limit` entries, which is useful beyond the annotations, but it says nothing about pagination, ordering, or what the XML payload looks like.

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 front-loaded sentence with the category tag first and the resource next; nothing is wasted. It is arguably too terse for the information an agent needs, but not padded.

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 should describe the returned XML danmaku shape, and it does not. Combined with an unexplained required `oid` and no guidance on the 1000-item limit ceiling, an agent cannot reliably invoke this without guessing.

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%, so the description must carry parameter meaning and it largely does not. It restates that `limit` bounds the result count, but leaves `oid` completely undefined even though it is the required parameter and its type (integer) makes it ambiguous whether it is an avid or a page cid.

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 (公开XML弹幕) scoped to a 分P, and the bracketed tag [字幕与弹幕] separates it from the subtitle tools. It is clear what it fetches, though it never states what 'oid' identifies (avid, bvid, or cid), which is central to the operation.

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 instead of bilibili_subtitles, bilibili_subtitle_text, or bilibili_comments, all of which are adjacent sibling tools. The only routing signal is the category tag, which implies but does not state that this is for danmaku rather than subtitles or comment threads.

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