get_gql_user_clips

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

Annotations are absent, yet the description only states the basic operation. It does not disclose read-only nature, authentication needs, or pagination behavior, leaving important gaps.

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 short but includes a redundant second line ('Get user clips') that echoes the name. It could be tighter but is not overly verbose.

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 4 parameters, lack of output schema, and no annotations, the description is incomplete. It omits pagination details, sorting behavior, and the effect of the flat parameter, which are essential for correct usage.

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 description coverage is only 25% (only 'flat' has a description). The description adds no value to parameters like user_id, max_id, or sort_by_views, failing to compensate for missing schema descriptions.

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 it returns the user's short video posts (reels), including the endpoint path. However, it does not differentiate from sibling tools like get_v2_user_clips or get_v1_user_clips_chunk.

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, nor any context on prerequisites or exclusions.

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