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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the mutation risk is carried by structured data rather than the description. The description adds no behavioral context such as irreversibility, required permissions, or what happens when id_or_name matches multiple objects, so it provides essentially nothing beyond the 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?

At two words there is no wasted verbiage, but the definition is under-specified rather than concise. It fails to front-load any of the scoping or target information an agent needs before invoking a destructive mutation.

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 six-parameter destructive mutation across three object levels, with no output schema and half the parameters undocumented, the description is entirely inadequate. An agent cannot determine scope, resolution behavior of id_or_name, or expected outcome from it.

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 50%, with folder, account, and language documented in the schema itself. The description adds no meaning for the three undocumented required parameters (level, id_or_name, new_name), notably the ambiguity of whether id_or_name accepts a display name or an ID. With half the schema covered, this sits at the minimum viable baseline.

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 'Rename an object' merely restates the tool name in generic terms and never names the resource domain. It is only via the title (campaign, ad set, ad) that an agent learns what kind of object is renamed, and it does nothing to distinguish this from sibling tools like snapchat_rename or tiktok_rename.

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 the platform-specific rename siblings, no prerequisites, and no mention of which account/folder context is required. The agent must infer everything from the schema.

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