tiktok get delivery status

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so this is clearly a safe read operation. The description adds little beyond 'simple diagnostics,' which is vague and doesn't disclose pagination behavior or response structure (though the output schema covers that). No contradiction with 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 of 11 words, with no filler or redundancy. It is front-loaded with the key action and scope, though the phrase 'simple diagnostics' is somewhat under-specified.

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 existence of an output schema and comprehensive parameter descriptions, the description is adequate but not rich. It lacks guidance on when to use the tool versus siblings and what 'simple diagnostics' entails, which an agent might need for correct selection.

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 has 100% description coverage for all five parameters, so the schema already explains limit, adgroupId, campaignId, includeAds, and advertiserId. The tool description provides no additional parameter meaning beyond what the schema offers.

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 the specific verb 'Aggregate' and names the resources (campaign, ad group, ad delivery status/operation_status). It clearly distinguishes from sibling tools like tiktok_get_campaigns or tiktok_get_adgroups by focusing on aggregate status and diagnostics.

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 guidance on when to use this tool versus alternatives such as tiktok_get_campaigns or tiktok_get_ads. No exclusions or conditions are provided; the agent must infer usage from the name alone.

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