get_gql_user_reposts

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

No annotations provided. The description does not disclose any behavioral traits such as pagination support (implied by the parameter repost_next_max_id), authentication requirements, or rate limits. It simply states the function.

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 contains repetition ('Get user's reposted content' and 'Get user media reposts'). It could be more concise by combining into one sentence. Still, it 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 the lack of output schema, annotations, and low schema coverage, the description is incomplete. It does not explain the response format, pagination logic, or how to use the pagination parameter. The flat parameter's effect is unclear without schema context.

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 description does not mention any parameters. Schema coverage is only 33% (flat parameter has a description), but the description adds no meaning beyond what is already in the schema. The repost_next_max_id parameter, which indicates pagination, is completely ignored.

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 states 'Get user's reposted content' and 'Get user media reposts', which clearly indicates the verb (get) and resource (user reposts). The tool name also includes 'reposts' which distinguishes it from siblings like get_gql_user_medias, but the description itself does not differentiate.

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 on when to use this tool versus alternatives. It does not specify prerequisites, typical contexts, or scenarios where other tools might be more appropriate.

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