tiktok get advertiser info

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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the fields returned, but this is likely redundant with the output schema. No additional behavioral context (auth, rate limits, pagination) is given, so it adds moderate value beyond 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?

The description is a single sentence, front-loaded with the verb and resource, and wastes no words. It efficiently communicates the tool's purpose and key return fields.

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 simple one-parameter tool with an output schema and strong annotations, the description is nearly complete. It clearly states the purpose and the parameter's role, though it lacks explicit routing guidance vs. siblings. This is a minor gap for such a focused 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 description coverage is 100%, so the sole parameter advertiserIds is fully documented in the schema. The description only hints that the IDs target 'specific' accounts, which is already implied by the schema name. Baseline 3 is appropriate because the schema carries the semantic load.

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 verb ('Get') and resource ('TikTok advertiser accounts') and enumerates the return fields (currency, timezone, status, balance). The qualifier 'specific' differentiates it from sibling tiktok_list_advertisers, so an agent can distinguish it without inspecting schemas.

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 when you need details for particular advertiser accounts, but it does not explicitly name alternatives or state when not to use it. With siblings like tiktok_list_advertisers, this leaves the agent to infer the selection logic, so it's adequate but not explicit.

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