Search your own captions

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

Beyond the readOnly/idempotent annotations, the description discloses a crucial behavioral caveat: a miss means the item is not in the last `scan` videos, not that it does not exist. It also reveals the local-filtering implementation, which helps an agent set expectations about completeness.

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 three short sentences with no filler. The action is front-loaded, followed by a brief implementation rationale and a vital caveat, so every sentence earns its place.

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 read-only search tool with fully documented parameters, the description covers purpose, local filtering behavior, and the open-world miss semantics. The annotations already provide the safety profile, and no output schema is needed to understand that this returns matching posts.

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?

The input schema already covers all parameters at 100% coverage, so the baseline is 3. The description adds extra meaning by tying `scan` directly to the miss semantics, clarifying that the search scope is limited to the most recent `scan` videos. It does not repeat schema details unnecessarily.

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 opens with a specific verb and resource: 'Find your posts whose title or description matches a query.' It also distinguishes itself from sibling list/get tools by explaining that TikTok has no native library search, so this tool pages recent videos and filters locally.

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 gives clear context for when this tool is appropriate: there is no TikTok-side search over your own library, so the tool compensates by scanning recent videos locally. It does not explicitly name alternatives such as list_videos, but the intended use case is evident.

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