get_v1_user_clips_chunk

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

The description discloses that responses include trial publications and that they lack a 'reshare_count' field, which is useful. However, it does not mention whether the operation is read-only or any potential side effects, and annotations are absent.

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 relatively short and front-loaded with the endpoint and core action. It includes a link for context, but some information could be more structured and concise.

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 lack of output schema and low schema coverage, the description partially compensates by noting trial publications and filtering. However, it does not explain pagination mechanics, error conditions, or return structure.

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% schema coverage, the description should compensate heavily. It explains that 'end_cursor' is for cursor-based pagination, but does not describe 'user_id' beyond implying it identifies the user. The name hints at the resource, but format details are missing.

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 chunk of user clips using a cursor, with a specific verb and resource. However, it does not explicitly differentiate from sibling clip tools like get_v2_user_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 other user data retrieval tools. Without this, an agent may choose incorrectly among many siblings.

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