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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds important behavioral context: it's a write operation (connecting a pixel) but not destructive, and it emphasizes that free businesses are blocked and permission checks must be done. This goes beyond annotations.

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 and front-loaded with the main action. However, the sentence 'Business and community refer to the same thing and are interchangeable' could be condensed, and the operational instructions add bulk. Still, it's clear and to the point.

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 minimal annotations, the description provides operational context (preconditions and restrictions) but lacks details on parameter meanings and expected return values. For a mutation tool, it covers necessary prerequisites but is incomplete in explaining the full 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?

Schema description coverage is 0%, and the description provides no explanation of the four required parameters (communityId, businessId, pixelId, accessToken). The description mentions 'pixel' but gives no semantics or validation details for any parameter.

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 action (connect a Facebook pixel to a managed community) and clarifies that 'business' and 'community' are interchangeable. However, it does not differentiate from sibling tools like 'connect_business_facebook_pixel' or 'authenticate_*' 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: check permissions first, call 'check_business_tool_access' before collecting inputs, show grace-period warnings, and never proceed when access is blocked. It also states that FREE businesses cannot use this tool regardless of feature rows. This is comprehensive and actionable.

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