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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious context: Meta turns several enhancements on by default and enhancements_on shows exactly what is live, which explains surprising results. It does not cover auth/connection prerequisites.

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 resource and its full field list, then covers usage. Mostly efficient, but the colloquial 'did Meta add music / touch up my video' phrasing and the closing default-on remark are slightly padded for a single-parameter read tool.

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 elaboration, and the description tells the agent what the creative read yields and why it matters. It omits the prerequisite that a Meta Ads account must be connected and how to obtain a valid ad_id, small gaps for a complex ad-tech surface.

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?

Only one parameter (ad_id) and schema description coverage is 0%, so the schema says nothing about it. The description implies it must reference an EXISTING Meta ad, but adds no format, source, or where-to-find-it guidance, so it only marginally compensates for the coverage gap.

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 (reads) and resource (an EXISTING Meta ad's creative) and enumerates exactly what it returns: headline, primary text, description, image/video, button, destination link, Page/Instagram actor, and enhancements_on. This distinguishes it from siblings like list_meta_ads and update_meta_ad_creative.

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?

Explicitly names when to use it and the alternatives: before duplicating an ad (copy_meta_entity) or rewriting it (update_meta_ad_creative), plus the user-question case about Meta adding music or touching up video. Nothing is left to inference.

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