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

Annotations are non-destructive and not read-only. Description adds behavioral context about permissions, free business restrictions, and pre-action checks, exceeding what annotations provide. 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?

Description is efficient, front-loads the purpose, and every sentence adds value. Slightly wordy with preconditions, but these are necessary for safe usage.

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 the simple tool (3 params, no nested objects, no output schema), the description covers prerequisites and restrictions well. It does not describe return values or error handling but is sufficient for an agent to invoke correctly.

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?

Input schema has 0% description coverage, and the description does not elaborate on any of the three parameters (communityId, pageId, accessToken). It only generically mentions 'inputs', failing to add meaning 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 states a clear verb and resource: 'Connect a Facebook page to the business for Magic Audience.' It distinguishes from sibling tools like disconnect_magic_audience_facebook_page and list_magic_audience_meta_pages.

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?

Provides explicit instructions: check business permissions, free businesses cannot use, call check_business_tool_access before collecting inputs, show warnings, and never proceed when blocked. Clearly defines when and when not to use.

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