Rename creative asset

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the rename is reversible, what identifier is returned, whether existing references to the asset break, or any auth/rate-limit 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?

It is a single short sentence with zero padding and is front-loaded, which is structurally clean. However, the brevity is under-specification rather than true conciseness — the same five words could have carried the parameter meaning and reversibility note.

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 mutation tool with a nested required parameter, no output schema, and 0% schema documentation, a one-line description is inadequate. An agent cannot tell from this definition what the new name parameter is or what to expect after the call.

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 0% across two parameters, including a nested data object, so the description carries full burden. "Rename" only faintly implies that data.name is the new name and gives no format, length, or uniqueness constraints, leaving the nested parameter effectively undocumented.

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 states a specific verb and resource ("Rename a creative asset"), which is clear and distinguishable from the get/delete/list siblings by name. However, it is a verbatim restatement of the title and adds no scope or differentiation beyond what the tool name already conveys.

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 siblings such as reddit_ads_upload_creative_assets or reddit_ads_delete_creative_asset, nor any prerequisites (e.g., asset must already exist, auth required). The agent must infer usage entirely from the name.

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