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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond them: it does not say the previous name is lost, that the rename applies immediately in the live TikTok account, or that name-based lookup may match multiple entities. No annotation contradiction exists, but the value-add is close to zero.

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 single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than disciplined editing. There is no structure indicating which parameter controls which object level.

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?

This is a destructive, open-world mutation with six parameters (two of them enums), a 50% documented schema, no output schema, and an ambiguous identifier parameter. A one-line description leaves an agent without the information needed to call it safely, and none of the gaps are covered elsewhere in structured fields.

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 only 50%, and the undocumented parameters are the critical ones: id_or_name has no description at all (is it an ID, a name, or either, and how is ambiguity resolved?), and new_name has bounds but no stated constraints or uniqueness rules. The description names neither parameter, so it does not compensate for the coverage gap.

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?

"Rename a campaign or ad group" restates the tool title almost verbatim and adds no scope detail beyond it. It does name a verb and the two object types, but an agent learns nothing new about what distinguishes this from the platform's other TikTok write tools (tiktok_set_status, tiktok_update_budget, etc.).

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 when-to-use guidance, no prerequisites (e.g. that the account must be enabled, or which folder to target), and no note about what to do if the name is ambiguous. Usage is only inferable from the tool name.

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