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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description's one piece of added behavior is the credit cost "(1 credit)", which is genuinely useful context not present in structured fields, but it says nothing about result volume, pagination termination, or what a page contains.

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 clauses, front-loaded with the action and resource, no filler. It is efficient, though the terseness means a useful sentence about pagination or scope could have been added without bloat.

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-only search with no output schema, the definition is minimally viable. It is missing pagination behavior (the cursor parameter implies multiple pages) and any hint of what a returned account record includes, which an agent would need to plan a search workflow.

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?

With 100% schema description coverage, the schema already explains that query is the search text and cursor comes from the previous page's data.cursor. The description adds nothing about query syntax, matching behavior, or pagination, 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?

"Search TikTok accounts by keyword" gives a specific verb (search) and resource (TikTok accounts), which distinguishes it reasonably well from siblings like tiktok_search_keyword and tiktok_search_hashtag. It stops short of naming those siblings explicitly, so the differentiation relies on the agent inferring that "accounts" means user profiles.

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 or when-not-to-use guidance and no alternative named, despite several closely related search tools (tiktok_search_keyword, tiktok_search_hashtag) in the sibling list. The agent must infer usage purely from the word "accounts".

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