tiktok_health_check

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states the operation is read-only and guarantees it never returns tokens or secrets, which are material safety behaviors. It does not describe failure modes or response shape, but the key non-mutating and secret-handling traits are covered.

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 two short sentences with no filler. The first sentence front-loads the operation and scope, and the second adds a concise security guarantee. 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?

For a low-complexity tool with one optional parameter, the description names the relevant objects and adds an important security guarantee. However, with no output schema, it stops short of indicating what a successful or failed health check returns, which is a notable gap for an agent invoking the 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?

The schema fully documents the single optional advertiserId parameter, including its fallback behavior from TIKTOK_ADVERTISER_ID to the first accessible advertiser. Since schema coverage is 100%, the description does not need to add parameter detail, 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 states a specific diagnostic operation ('health check') and names the exact resources involved: TikTok credentials, accessible advertisers, and advertiser info. This clearly differentiates it from the many get_* sibling tools, which fetch specific data rather than check overall health.

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 phrase 'read-only health check' implies use for verifying TikTok access and advertiser availability, but no explicit when-to-use guidance, exclusions, or alternative tool comparisons are provided. The agent must infer the trigger condition from the tool name and description.

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