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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this mutates live ad entities. The description adds nothing beyond that: it does not say whether the old name is recoverable, whether the change is logged or audited, what happens if id_or_name is ambiguous, or whether permission scopes are required.

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?

A single front-loaded sentence with zero waste, but what is there is essentially a restatement of the title plus an enumeration of the level enum. It is short rather than efficient, since the brevity comes at the cost of missing information.

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 write operation with no output schema and half of its parameters undocumented, so the description carries a heavy burden and does not meet it. An agent cannot tell from the definition how to resolve the target entity or what the response will confirm.

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?

Six parameters with only 50% schema description coverage, and the description contributes nothing for any of them. In particular id_or_name is entirely unexplained (is it an ID, a name, or either? does it accept partial matches?), and the optional folder/account scoping parameters go unmentioned.

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?

States a specific verb (Rename) and the three resource levels it operates on (campaign, ad squad, ad), so the operation itself is unambiguous. However, it does not identify the platform as Snapchat in the description text, which matters given the sibling tools meta_rename and tiktok_rename that share the same verb.

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?

Contains no when-to-use or when-not-to-use guidance, and never routes the agent to an alternative such as snapchat_set_status or snapchat_duplicate. Prerequisites like needing a folder or ad account selected are not mentioned at all.

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