bili_favorite_update

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

No annotations are supplied, so the description carries the full burden; it does disclose the auth prerequisite (favorite permission), the ownership restriction, single-item granularity and no batching. It says nothing about idempotency, what happens on repeated calls, rate limits, or what is returned, which matters for a mutation tool.

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 short, front-loaded sentences with the scope constraints leading and the parameter hints trailing; no filler. The 'defaults OFF' clause is the one piece that adds ambiguity rather than information.

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 four-required-parameter mutation with zero schema coverage and no annotations, the description leaves the most cryptic field (action_id) undefined and never clarifies the bvid/media_id pairing. The output schema existence lowers the need to describe returns, but the input-side gaps remain significant.

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% with four required parameters, and the description only glosses 'Folder ID string' (presumably media_id) and hints at 'enabled' via 'defaults OFF'. bvid and especially action_id — an non-obvious required string — get no explanation at all.

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 pair (add/remove) and resource (ONE video in ONE own favorite folder), which clearly separates it from the read-only favorites siblings (bili_favorite_lists, bili_favorite_content). The scope qualifiers are strong, but 'defaults OFF' sits awkwardly next to a required 'enabled' parameter and muddies what the operation does by default.

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?

Gives real preconditions and exclusions: requires favorite permission, must be your own folder, exactly one video, no batch. It does not name a sibling alternative or say when to prefer a different tool, so it stops short of the top band.

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