get_v1_user_followers_by_secUid

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond them: one page per call, live request to TikTok, billed per call, and the default page size. It doesn't mention rate limits, follower ordering, or what happens at the end of pagination, keeping it short of a 5.

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?

Three dense sentences, front-loaded with the primary action and scope, then routing, then pagination mechanics. Every clause carries information and nothing is repeated from the schema.

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?

There is no output schema, and the description partially compensates by naming the response field next_page_id and the pagination contract. It stops short of describing the follower record shape or end-of-list behavior, which would fully close the gap for a paged read tool.

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%, so the description must carry weight, and it does: it defines count as page size with a default of 30 and explains that page_id should be fed from the previous response's next_page_id. Only the secUid format (pattern/length, already in schema) is left unelaborated.

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 a specific verb and resource ('List a TikTok user's followers by secUid'), scopes the behavior ('one page per call'), and names the sibling it is not ('use get_v1_user_followers_by_username when you only have a handle'). An agent can distinguish it from the many other get_v1_user_* siblings without opening a 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?

It gives an explicit trigger ('use it when you already have the secUid from a profile') and an explicit alternative with its own selecting condition. It also explains the pagination workflow (pass next_page_id as page_id), leaving no inference required.

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