search_bilibili_videos

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not mention authentication requirements, rate limits, pagination behavior, or whether the operation is read-only. The word 'Search' implies a read operation, but no explicit behavioral context is given.

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 compact and front-loaded with the action, followed by a terse, well-organized Args block. No wasted words; it earns its length by documenting parameters that the schema leaves undescribed.

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 simple search tool with an output schema, the parameter documentation is adequate. However, the description omits whether Bilibili credentials must be configured first (sibling test_bilibili_credentials exists) and does not clarify when to use this tool over other Bilibili list/search tools. This leaves moderate context gaps.

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?

The schema has zero descriptions on its properties, so the Args section is essential. It adds meaning by listing all three parameters, their roles, defaults, and the valid 'order' values (totalrank, click, pubdate, dm, stow), which the schema itself lacks. It does not explain what each sort value means, but it provides functional coverage.

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 ('Search') and resource ('Bilibili videos') with a keyword filter, making the primary function unambiguous. It implicitly differentiates from siblings by platform (e.g., search_youtube_videos), though it does not explicitly name alternatives. A clear purpose with minor room for explicit sibling differentiation.

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?

Provides no guidance on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or when to prefer a sibling like get_bilibili_user_videos or search_youtube_videos. The agent must infer usage from the tool name alone.

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