List popular TV shows

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds valuable context by stating the data source ('showfeed.site'), the recency qualifier ('recently'), and the lack of authentication requirement. This goes beyond the annotations without contradicting them.

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, clear sentence that front-loads the action and includes only essential information. Every word contributes meaning, with no redundancy or filler.

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, parameterless list tool, the description covers the key aspects: what data is returned (popular shows), the source, recency, and auth requirements. While the exact return format isn't described, the annotations and simplicity of the tool reduce the need for additional detail.

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 tool has zero parameters, so the schema fully covers everything. The baseline for zero params is 4, and the description doesn't need to add parameter-related details beyond confirming no inputs are required.

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 tool returns the most viewed shows on showfeed.site recently, using a specific verb ('Returns') and resource ('shows most viewed'). This distinguishes it from sibling tools like shows_search and shows_get, which focus on searching or fetching specific show details.

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 provides clear context by noting it returns recently popular shows and that no sign-in is required, which is essential for an agent deciding whether to invoke it. While it doesn't explicitly name alternatives, the zero-parameter nature and clear scope make the intended use obvious.

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