get_v1_user_suggested_by_secUid

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

Annotations already cover safety (readOnlyHint, destructiveHint=false) and openness (openWorldHint), so the description's added value is the billing/live-call disclosure ('Live request to TikTok, billed per call') and the one-page-per-call pagination behavior. It does not describe rate limits or failure modes, 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?

Four tight sentences: purpose, sibling routing, pagination mechanics, cost. Front-loaded with the core operation and zero 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, the description still tells the agent how to paginate (read `next_page_id` from the response) and that the call is billed. Combined with annotations covering safety, an agent has everything needed to invoke it correctly.

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 33%, so the description carries real weight: it explains `count` sets page size (default 30) and that `page_id` should be fed the previous response's `next_page_id`. The `secUid` format/length constraints remain schema-only, but the description meaningfully supplements the undocumented params.

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 ('List') and resource (TikTok suggested/related accounts) scoped by `secUid`, and explicitly distinguishes itself from the sibling `get_v1_user_suggested_by_username` by identifier type. An agent can select it 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?

Gives an explicit condition for use ('when you already have the `secUid` from a profile') and names the alternative tool plus the condition that selects it (only a handle). No inference required.

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