tiktok_get_advertiser_info

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

With no annotations, the description carries the behavioral burden. It clearly signals a read-only operation through 'Get' and enumerates the returned fields, which is useful. However, it does not disclose error behavior, authorization requirements, rate limits, or output envelope details.

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 a single efficient sentence with the action, target, and key output fields front-loaded. There is no filler or redundant terminology.

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 required parameter, no nested objects, and no output schema—the description provides enough to invoke the tool: it identifies the operation, the resource, and the primary return fields. It could be more complete by suggesting related tools for obtaining advertiser IDs, but that is a minor gap.

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 sole parameter advertiserIds is already fully documented in the schema ('One or more advertiser IDs'). The description adds little beyond restating that the call targets advertiser accounts, so it does not meaningfully improve parameter understanding.

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 uses a specific verb ('Get') and resource ('TikTok advertiser accounts') and lists concrete return fields: currency, timezone, status, balance. The word 'specific' distinguishes it from listing siblings like tiktok_list_advertisers, though it does not explicitly name an alternative.

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 explicit when-to-use guidance, no exclusions, and no mention of alternatives such as tiktok_list_advertisers for first obtaining advertiser IDs. The 'specific' wording loosely implies the agent should already have IDs, but this is not developed into actionable guidance.

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