tiktok_open_search

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

With no annotations, the description carries the full burden. It discloses that the tool retries tapping the magnifier 'a few points' and outlines the sequence of actions. However, it does not explain error handling, waiting behavior, or what happens after submission.

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?

The description is concise at two sentences, but includes vague terms like 'wide [input]' that reduce clarity. It front-loads the main action and is structured, but a slight improvement in wording would make it fully effective.

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?

The tool has a single optional parameter and no output schema. The description explains the UI steps, but does not cover preconditions (e.g., is the app already open?) or postconditions (e.g., is the search result page loaded?). It is adequate but incomplete for a UI navigation 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 description coverage is 100% for the single parameter (maxTries). The description adds 'retries a few points', which is consistent but less precise. It does not provide additional meaning beyond what the schema already offers, so baseline 3 is appropriate.

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 clearly states the tool's purpose: to open the TikTok search landing from the For You feed by tapping the magnifier, then typing and submitting a search. It uses specific verb+resource and distinguishes from a similar UI button ('Not the narrow 搜尋 submit button'), making it unambiguous.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It only differentiates from a UI element (not a sibling tool) and lacks explicit when-to-use or when-not-to-use conditions.

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