playlet-bili-feed

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

With no annotations, the description carries the disclosure burden. It reveals the daily 15:00 update schedule, the previous-day data lag, the strict date-validity rule, and the no-automatic-fallback behavior. It does not describe the output shape or error behavior, but those are secondary for a simple read-only feed query.

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 a single compact sentence that front-loads the purpose and sorting behavior, then packs the important update and date rules without redundancy. Every phrase 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?

For a low-complexity tool with two optional parameters, a fully documented schema, and no output schema, the description provides all essential operational context: platform, content type, ordering, update cadence, and date constraints. Nothing critical is missing for correct invocation.

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%, so the baseline is 3. The description adds meaningful semantics to the date parameter: it must not exceed the latest data date and no-data dates must be confirmed before querying. The count parameter receives no additional description beyond the schema, preventing a 5.

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 states a clear verb-resource pair: query Bilibili short-drama hit-list works by date, sorted by likes. It distinguishes itself from sibling tools like playlet-douyin-feed and general bilibili search/download tools by naming both the platform (B站) and the content type (短剧爆款榜).

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 gives explicit usage constraints: dates must be ≤ the latest data date, no-data dates require confirmation, and automatic fallback is prohibited. It does not explicitly name alternative tools when not to use it, but the sibling names and platform/content scoping make the selection context reasonably clear.

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