hotlist

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'hotList' reveals nothing about whether this is a read or write operation, what data it returns, whether it requires authentication, has rate limits, or any other behavioral characteristics. This leaves the agent completely in the dark about how the tool behaves.

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?

While technically concise with a single word, this is under-specification rather than effective brevity. The description fails to provide any meaningful information that would help an agent understand or use the tool. Every word should earn its place, but this single word doesn't earn its place by adding value.

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 complete lack of annotations, no output schema, and a description that provides zero operational context, this is completely inadequate. The agent cannot determine what this tool does, when to use it, what it returns, or how it behaves. The description fails to provide the minimal information needed for effective tool selection and 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?

With 0 parameters and 100% schema description coverage, the schema already fully documents the input requirements (none). The description doesn't need to compensate for any parameter gaps, so it meets the baseline expectation for a parameterless tool. However, it doesn't add any value beyond what the schema provides.

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?

Tautological: description restates name/title.

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 offers no guidance on when to use this tool versus alternatives. With 70+ sibling tools including 'hotvideolist', 'list', 'recommend', and others that might serve similar purposes, there is zero context about appropriate usage scenarios, prerequisites, or exclusions.

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