whale_search

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false. The description adds one genuinely useful datum: the local login requirement, which is an authorization prerequisite not captured by the annotations. However, 'upstream WBI implementation' is internal jargon that does not disclose behavior, and pagination limits or failure modes are unmentioned.

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?

One compact sentence with the core action at the front. The WBI implementation clause is the only part that does not clearly justify 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?

There is no output schema and no description of what a search result contains (video fields, ordering, paging behavior beyond the schema's maximum), and parameters are undocumented. For a discovery tool, an agent is left guessing about the results and the page cap.

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%, so the description has to explain both parameters. It says nothing about 'keyword' semantics or about the 'page' parameter's hard cap of 5, which meaningfully limits how callers use results.

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: search Bilibili videos. It is distinguishable from siblings like whale_popular or whale_video, but it does not explicitly say how it differs from any of them.

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?

It names a prerequisite ('requires local login') but gives no guidance on when to use this search instead of the sibling listing tools such as whale_popular, or what the search covers.

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