Update ad

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

Annotations already declare write (readOnlyHint=false) and non-destructive behavior, so the description's job is to add nuance it does: partial-update semantics, deletion-via-status-field, and an immutable field (ad group). It does not cover auth/rate limits or what the response returns, but the added behavioral detail is substantive beyond the structured hints.

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?

Four short, front-loaded sentences, each carrying a distinct rule (purpose, patch semantics, deletion, immutability) with zero filler. Nothing is redundant or out of order.

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 an update tool with annotations and no output schema, the description covers the mutation model, deletion route, and a key constraint, which is nearly all an agent needs to invoke it correctly. It stops short of mentioning auth requirements or the shape of the returned updated ad.

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 coverage is only 50%: the 'data' object enumerates allowed fields, but ad_id is undocumented and the field list is untyped. The description compensates with patch semantics and the immutability constraint on the ad group, but does not clarify value formats or which fields are required. Baseline 3 for a partially-covered 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?

States a specific verb+resource ('Update an ad') that an agent can immediately distinguish from list/get/create siblings. It does not explicitly differentiate from adjacent tools such as reddit_ads_update_ad_group or reddit_ads_set_status, so it stays at 4 rather than 5.

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?

Gives concrete operational guidance: patch semantics ('Pass only the fields to change'), the deletion path ('set configured_status to DELETED'), and a hard constraint ('The ad group cannot be changed'). It lacks any when-to-use-vs-alternative routing (e.g., versus reddit_ads_set_status), which keeps it from a 5.

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