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

Annotations already establish readOnly, openWorld, and non-destructive behavior. The description adds the data sections returned and the campaign filter, but it does not cover freshness, pagination, or how detail=summary vs full changes output, so it adds only moderate behavioral context.

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 one compact, front-loaded sentence with no filler. It could be slightly more complete, but every phrase maps to the resource or returned data.

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 9-parameter reporting tool with no output schema, the description gives a useful field list but omits the summary/full default behavior and the date/account/folder context. The schema handles most parameter meaning, but the description leaves some gaps about output shape and intended granularity.

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 89%, so the schema already defines most parameters. The description only reinforces the campaign filter and lists return fields, adding little semantic detail beyond the schema.

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 identifies the exact resource (TikTok ad groups) and enumerates the fields returned, so the agent knows this is a read/list tool for ad-group data. It does not explicitly contrast with sibling tools such as tiktok_campaigns or tiktok_ads, so it stops short of full sibling differentiation.

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 only usage hint is 'Filter by campaign,' which points at one parameter but does not explain when to choose this tool over tiktok_campaigns, tiktok_ads, or tiktok_performance. No when-not-to-use conditions are given.

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