bili_favorite_content

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

No annotations exist, so the description carries the full burden; it does disclose pagination behavior and stable snapshot cursors, which is valuable non-obvious behavior. It does not say what 'accessible' means (auth/permission scope) or whether results are cached/snapshotted across cursor calls in a way that could go stale.

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?

Two compact sentences, front-loaded with the read action and followed by the behavioral note and exclusion. No wasted words, though the telegraphed phrasing ('native server pagination', 'stable snapshot cursors') is dense for its length.

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?

An output schema exists so return values need not be described, and pagination is covered. However, for a 3-parameter tool at 0% schema coverage, the description leaves the meaning of media_id and the access condition of 'accessible' unexplained, which an agent needs to call it correctly.

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 compensate and it largely does not: it alludes to pagination (limit/cursor) via 'native server pagination plus stable snapshot cursors' but never defines cursor stability semantics, and never explains media_id or what a 'folder' identifier is.

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 and resource ('Read accessible folder videos') with a clear scope, and the negative clause 'No favorite/unfavorite action' helps separate it from bili_favorite_update. It does not, however, distinguish itself from bili_favorite_lists, which an agent would need to tell apart.

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 'No favorite/unfavorite action' implicitly routes mutation intent to bili_favorite_update, which is useful. But there is no explicit statement of when to call this versus bili_favorite_lists or bili_user_videos, and no prerequisites or access conditions are given.

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