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

Annotations indicate readOnly=false and destructiveHint=false, so the tool is a mutating operation. The description adds context about permission checks and tier restrictions, which help the agent understand when to proceed. No contradiction with 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 a single paragraph with multiple sentences, each carrying important information. It is relatively concise but could be improved with structured formatting (e.g., bullet points for preconditions).

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 thoroughly covers preconditions and permissions but lacks information on return values, side effects, or what happens after a successful connection. With no output schema, this gap is notable.

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 coverage is 0%, yet the description does not explain any of the four required parameters (communityId, businessId, pixelId, accessToken). It only mentions that business and community are interchangeable, which is insufficient for parameter understanding.

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's purpose: 'Connect a Facebook pixel to a managed community.' It also explains that business and community are interchangeable. However, it does not differentiate from the sibling tool 'connect_community_facebook_pixel', which may cause confusion.

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 usage guidelines: check business permissions, note that FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, and show grace-period warnings. 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.