search_bilibili_videos

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

With no annotations, the description carries the full burden. It states the tool does not auto-fetch subtitles/comments/reorder and requires credentials. However, it does not disclose error handling behavior (e.g., on invalid credentials), rate limits, or whether the output is always ordered. The behavioral disclosure is adequate but not thorough.

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 two sentences: the first states the main purpose and constraints, the second covers prerequisites and a pointer to a sibling tool. No redundancy, every sentence earns its place.

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?

Given the presence of an output schema (not shown but marked as true), the description need not detail return values. It covers the tool's core purpose, limitations, and prerequisites. It could mention what happens on credential failure or empty results, but overall it is sufficiently complete for a simple search tool.

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 100%, so the schema already documents parameters. The description adds value by explaining the default limit (5) and maximum (10), the trimming and length constraints for query, and the meaning of the output ('candidate metadata'). This context improves usability beyond the schema alone.

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 clearly states the verb 'search', resource 'Bilibili videos', and the scope: keyword-based, returns up to 10 sorted candidates. It explicitly distinguishes from siblings by stating it does not auto-fetch subtitles, comments, or reorder.

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 explicitly requires configured and logged-in Bilibili Cookie, and suggests calling get_credential_setup_instructions for help. This provides clear guidance on prerequisites and when to use the setup tool. However, it does not explicitly mention when to prefer other search-like tools (e.g., list_bilibili_favorite_videos) over this one.

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