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

Annotations already indicate readOnlyHint=true. The description adds behavioral context such as requiring business permission checks and access validation, which goes beyond the annotations. No contradiction.

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 relatively concise, with the purpose front-loaded and additional guidelines in subsequent sentences. Every sentence adds value, though it could be slightly more streamlined.

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?

The description covers usage prerequisites but does not hint at the return value (likely boolean). Given the tool's simplicity and lack of output schema, the description could be more complete by indicating the output type or behavior.

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?

There is one parameter (communityId) with 0% schema description coverage. The description does not explain the parameter's meaning or expected format, even though the name is self-explanatory. The description should add semantic context beyond the schema.

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 tool checks whether a community has Magic Ads connected. It uses a specific verb and resource, and the purpose is distinct from sibling tools like get_magic_audience_campaign, which provide detailed campaign data. However, it doesn't explicitly differentiate itself from siblings.

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: before offering the action, check business permissions, call check_business_tool_access, and never proceed when access is blocked. It also notes that FREE businesses cannot use it, offering a clear usage context.

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