tiktok health check

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a valuable security guarantee—'Never returns tokens or secrets'—which goes beyond the annotations and provides critical behavioral context for an agent handling credentials. It does not contradict annotations.

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, front-loaded sentences with zero filler. The core purpose ('Read-only health check') leads immediately, and the security note is a concise addition. Every word 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?

Given the low complexity (one optional parameter), existing output schema, and annotations covering safety, the description is complete. It tells the agent what the tool checks and what it guarantees not to return, leaving no critical gaps for correct invocation.

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 optional parameter, so the schema fully documents advertiserId, including its default behavior. The description adds no additional parameter-level detail, which matches the baseline for full schema coverage.

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 a specific verb ('health check') and resource (TikTok credentials, accessible advertisers, and advertiser info). It distinguishes itself from sibling data-retrieval tools by framing it as a diagnostic check, not a data pull. The purpose is 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 implies usage as a verification/health-check tool but does not explicitly state when to use it versus alternatives (e.g., tiktok_list_advertisers or tiktok_get_advertiser_info). No exclusions or conditional guidance are provided, leaving the agent to infer its role from the 'health check' label.

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