bilibili_user_feed

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that the dynamics are 'public', implying no auth or private-content access is required, but nothing about pagination behaviour or what a returned item 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?

The single bracketed sentence is front-loaded and free of filler. It is efficient, though its brevity spills over into under-specification rather than tightness.

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 two-parameter list tool with no output schema and 0% schema coverage, the description should cover pagination and the meaning of host_mid. Neither is addressed, so an agent must guess how to page through results.

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 explain both parameters; instead it only hints that host_mid identifies the uploader. The offset parameter, which controls pagination, is not mentioned at all, leaving the schema to carry undocumented meaning.

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 concrete verb (读取) and resource (公开动态) scoped to a specified uploader (指定UP主), which implicitly separates it from bilibili_my_feed (the caller's own feed). It does not, however, distinguish it from bilibili_dynamic_detail, which also returns dynamics.

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_my_feed, bilibili_dynamic_detail, or bilibili_user_videos, nor any prerequisites such as needing a valid host_mid. Usage must be inferred entirely from the name.

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