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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description's 'List' operation is consistent. However, the description adds crucial behavioral context beyond annotations: business permission checks, free tier ineligibility, and the need for pre-access verification. It does not mention pagination or error behavior, but the procedural constraints are valuable.

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 concise, with a single sentence for purpose followed by procedural instructions. It is front-loaded with the main action. However, the instructions are somewhat dense and could be structured into bullet points for improved readability. Overall, it is efficient with minimal redundancy.

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 no output schema and 4 undocumented parameters, the description should explain the return format (list of campaigns) and parameter purposes. It does neither. The tool's use case (listing campaigns) is implied by the name but not elaborated. Important context like pagination behavior and the role of productRefs is missing, making the tool definition incomplete for an AI agent.

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 4 parameters (page, limit, communityId, productRefs) with 0% description coverage. The description does not explain any of these parameters (e.g., page/limit for pagination, productRefs for filtering). With no parameter descriptions in the schema, the description must compensate but fails to do so, leaving the agent without guidance on how to fill the parameters.

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 the verb 'List' and the resource 'Magic Audience / Magic Ads campaigns' with a specific scope ('for a managed community'). The tool name is echoed, but the description adds meaningful context about the resource type and scope, distinguishing it from sibling list tools.

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 on when to use the tool: it requires checking business permissions, is not available for FREE businesses, and mandates calling check_business_tool_access before inputs. It also instructs on handling grace-period warnings and resubscribe links, and states never to proceed when access is blocked. This is comprehensive and clearly excludes false usage.

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