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

Annotations already indicate readOnlyHint=true and destructiveHint=false, aligning with a list operation. The description adds valuable behavioral context such as the restriction for FREE businesses and the requirement to check permissions, which goes beyond the 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 well-structured with a clear logical flow, but it is slightly verbose (e.g., explaining interchangeability of business/community). It could be more concise without losing important guidance.

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?

For a list tool with 3 parameters and no output schema, the description provides essential context about permissions and prerequisites. However, it does not describe the return format or what the listed pixels include, which would be helpful for completeness.

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?

The description has 0% schema coverage and does not explain the meaning of the three parameters (communityId, businessId, facebookAccessToken). Given the low coverage, the description should compensate, but it fails to provide semantic clarity for each 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 'List Facebook pixels for a selected business during community tracking setup', specifying the verb 'list' and the resource 'Facebook pixels', and distinguishes from similar sibling tools like list_business_facebook_business_pixels by mentioning the community tracking context.

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 business permissions, call check_business_tool_access first, FREE businesses cannot use it, show warnings and resubscribe link, and never proceed when access is blocked. This clearly defines when and how to use the tool, including prerequisites and exclusions.

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