get_user_clips

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

The description indicates a read-only operation ('Recupera') and a time-window filter, but no annotations are present to confirm safety or output traits. It does not explain what 'más populares' means, the return format, or edge cases such as no clips found, leaving the agent to infer these details.

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 entire description is one focused sentence with no filler, front-loading the verb and resource. It is concise and easy to parse.

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?

The description provides the core purpose but lacks necessary context for a tool with no output schema and no annotations: response format, sorting rule behind 'más populares', and behavior when no clips exist or the window is empty. It is sufficient for invoking the tool but not fully self-contained.

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?

All three parameters are documented in the schema (100% coverage), so the description does not need to add parameter semantics. The phrase 'ventana de tiempo configurable' mirrors the window_days parameter description but adds no new information about limit or login.

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 retrieves a channel's most popular clips within a configurable time window, using the specific verb 'Recupera' and a concrete resource ('clips más populares de un canal'). This distinguishes it from siblings like get_user_videos, which concern videos rather than clips.

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?

No guidance is provided on when to use this tool versus alternatives such as get_user_videos or check_user_live. The description only restates the function without exclusions, prerequisites, or alternative tool references.

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