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

Annotations already flag this as non-read-only, destructive, non-idempotent and open-world, so the safety profile is covered. The description adds real context beyond that: only the targeted ad stops while neighbors keep delivering, the three status values and their plain-language meaning, and confirm=false as a preview/dry run. Auth requirements and rate limits remain unstated, hence not a 5.

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?

Front-loads the action and scope in the first clause, then adds operational detail in tight, pipe-separated fragments. Every sentence adds information; nothing is redundant padding.

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?

An output schema exists so return values need no explanation, and the mutation semantics, status vocabulary and preview path are all covered. The only gap is account_id, which is required but never described, leaving a small documentation hole for a 5-param tool.

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 0%, so the description carries the burden and does so for most fields: ad_id's origin, the full meaning of each status value, and confirm's preview semantics. Renaming is implied via "renames it" but the name parameter is never explicitly tied to it, and account_id is 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?

Names specific verbs (pauses, resumes, archives, renames) against a specific resource (ONE Meta ad), and immediately bounds scope to a single ad. An agent can distinguish this from delete_meta_ad, update_meta_ad_creative, and update_meta_adset without opening a schema.

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 a concrete trigger ("switch off one ad that is wasting budget") and states where the identifier comes from (list_meta_ads). It stops short of naming alternatives or exclusions, e.g. when to prefer delete_meta_ad over ARCHIVED, so it lacks the explicit when-not guidance of a 5.

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