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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the credit cost, which is useful operational context, but says nothing about pagination behavior, result caps, or private-account handling — gaps that matter for a paginated list endpoint.

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?

Two short fragments with zero padding, and the core purpose is front-loaded. However, the extreme terseness is under-specification rather than disciplined conciseness — it omits context an agent would benefit from at essentially no length cost.

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?

For a simple two-parameter read tool with full schema coverage and annotations, the essentials are present. With no output schema, though, the description gives no hint of what a returned record looks like or how pagination terminates, leaving the agent to discover these at call time.

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 100%, with both 'handle' (with or without @) and the pagination 'cursor' fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 the resource precisely: 'Accounts a TikTok profile follows', which is clearly distinct from the sibling tiktok_followers (accounts following the profile). It does not name the sibling explicitly, so it falls short of a 5, but an agent can infer the direction of the relationship from the wording.

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?

There is no when-to-use guidance, no mention of when to prefer tiktok_followers or tiktok_profile instead, and no prerequisites or pagination guidance. The implied use case (enumerate who a user follows) is only inferable from the noun phrase.

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