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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context about business permissions and free business restrictions, which is valuable beyond annotations. However, it does not detail error handling or return behavior beyond a simple get.

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?

The description is a single sentence for purpose, followed by a block of usage guidelines. It is front-loaded and to the point, with no unnecessary words. A minor trim could improve, but it is already efficient.

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?

Given the simple tool (3 parameters, no output schema) and thorough usage guidelines, the description is fairly complete. It lacks description of the return object, but for a get operation, that is not essential. The permissions context is well-covered.

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?

Input schema has 3 required parameters (adId, campaignId, communityId) with 0% schema description coverage. The description provides no explanation of these parameters, their formats, or how to obtain them. Although the names are somewhat self-explanatory, the tool should compensate given the low coverage.

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 clearly states 'Get one Magic Audience ad object for a campaign.' It uses a specific verb ('get') and resource ('Magic Audience ad'), and distinguishes from sibling tools like create_magic_audience_ad and update_magic_audience_ad by implying a read operation.

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?

The description provides explicit guidance: check business permissions, FREE businesses cannot use it, call check_business_tool_access before input collection, show warnings and resubscribe links, and never proceed when access is blocked. This clearly tells when and how to use the tool.

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