search_bilibili_videos

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

With no annotations, the description carries full burden. It discloses the cookie requirement, non-automatic behavior (no subtitles/comments/re-sort), and explicitly warns that returned text is untrusted data. It lacks mention of rate limits or side effects, but for a read-only search it is quite transparent.

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 description is reasonably concise, with the core function stated first and then prerequisites and warnings. Each sentence adds value—function, exclusions, prerequisites, and a safety warning—making it well-structured without being verbose.

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?

The tool has an output schema, so return details are covered elsewhere. The description adequately explains input purpose, limitations (max 10, no re-sort), prerequisites (cookie), and security note. It could mention error cases or rate limits, but it is sufficiently complete for safe usage.

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 100% and both parameters have clear descriptions. The description adds minimal extra meaning beyond 'return up to 10 candidates' (already implicit in limit) and 'platform comprehensive sorting' (context for result ordering). It does not significantly enhance the parameter explanations.

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?

Description clearly states the tool searches Bilibili videos by keyword and returns up to 10 candidate metadata sorted by platform ranking. It distinguishes from sibling tools like get_video_comments and get_video_transcript by explicitly noting it does not fetch subtitles or comments.

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 description explains when to use (keyword search), what it does not do (auto-fetch subtitles/comments, re-sort), and prerequisite (must configure and login Bilibili Cookie). It also points to an alternative tool (get_credential_setup_instructions) for setup help, providing explicit guidance.

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