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

Annotations declare readOnlyHint=true and destructiveHint=false, consistent with description. Description adds behavioral context: FREE businesses cannot use this tool, and access checks are required. No contradictions.

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?

Description is three sentences: first sentence defines purpose, second clarifies terminology, third provides usage instructions. While the third sentence is long, it is efficient and front-loaded with important information.

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?

Description covers usage context and restrictions, but lacks information about output/return value. With no output schema, describing the return format would improve completeness. Sibling list provides context but not within description.

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?

Parameter schema has 0% coverage, and description does not explain the meaning or constraints of businessId, communityId, or facebookAccessToken. The phrase 'selected business' implies businessId but no explicit mapping. Missing parameter-level details.

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', the resource 'Facebook pixels for a selected business', and the context 'during community tracking setup'. It distinguishes from sibling tools like list_business_facebook_businesses and list_community_facebook_business_pixels.

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?

Explicitly states when to use (during community tracking setup), prerequisites (check business permissions, call check_business_tool_access), and actions to take if access is blocked (show grace-period warning, verified resubscribe link). Also clarifies that business and community are interchangeable.

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