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

Annotations already carry the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=false), and the description adds a useful scope clarification, 'Does not modify advertising'. It does not explain the readOnlyHint=false posture or what the 'fresh' flag triggers, so it adds modest context beyond the structured fields.

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?

Two tight sentences with the core purpose front-loaded and the non-modifying caveat last. No filler; every clause carries information, though the second sentence slightly overlaps the destructiveHint=false annotation.

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 description covers the basic contract of a structural read over a date range. Gaps remain in usage guidance and the undocumented 'fresh' parameter, so it is adequate but not complete.

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%, so the description must carry parameter meaning, yet it only implicitly covers since/until ('explicit reporting period') and campaignId ('campaign'). brandId and the 'fresh' boolean are entirely undocumented in both schema and description, leaving a real 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 ('Read') and resource ('Meta advertising campaign, ad sets and ads') scoped to a reporting period, so an agent can distinguish it from a generic campaign read like get_campaign. However, it does not explicitly name the sibling ad tools (get_ad_performance, get_ad_breakdown) it sits beside, so differentiation is left partly to inference.

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 when-to-use guidance and no alternative is named, despite a dense set of sibling ad tools (get_ad_performance, get_ad_breakdown, get_ad_watch, get_campaign). Nothing tells the agent when this structural read is preferred over a performance read.

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