get_v2_user_likes_by_secUid

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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds material context beyond them: 'one page per call', 'Live request to TikTok, billed per call'. Cost and pagination semantics are exactly the kind of thing annotations cannot express.

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?

Front-loads the resource, then sibling routing, then parameter semantics, then cost/pagination, then the raw endpoint. Every sentence carries distinct information with no 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?

With no output schema and low schema coverage, the description supplies pagination mechanics and billing, which is what an agent needs to call this safely. Return shape is not described, but the pagination note implies the page structure adequately.

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 coverage is only 33% (only secUid is documented in the schema), so the description must compensate — and it does: count = page size, cursor = page-through mechanism, secUid sourced from the profile tool. It omits the count max of 50, which the schema carries.

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?

States a specific verb+resource ('List videos a TikTok user has liked') and explicitly distinguishes itself from the sibling get_v2_user_medias_by_secUid. An agent can pick between the two without opening either schema.

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?

Names the alternative tool and the condition that selects it ('for the user's own videos'), and tells the agent where secUid comes from. No explicit when-not-use guidance beyond the sibling pointer, but the routing is clear.

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