ghl_social_attach_facebook_page_group

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

Annotations already indicate this is a non-read-only, non-destructive mutation. The description adds only the endpoint URL and version, which do not disclose behavioral traits like auth requirements, rate limits, side effects (e.g., does it replace existing attached pages?), or error conditions. 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 very short but includes technical endpoint details that are likely not useful for an agent selecting the tool. It is concise but under-specified, lacking necessary context to be actionable.

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 complexity of attaching a Facebook page/group and the existence of many similar sibling attach tools, the description is incomplete. It does not explain the process, prerequisites (e.g., OAuth integration), or what the body fields represent. No output schema, and the description fails to compensate.

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?

Despite 100% schema coverage, the description does not explain the parameters beyond what the schema provides. The body fields are undocumented in the description, and their purpose is unclear. The description adds no additional meaning to aid the agent in constructing valid inputs.

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 the verb-resource combination 'Attach facebook pages' clearly, and the endpoint confirms it attaches a Facebook account. However, it does not differentiate from sibling attach tools like ghl_social_attach_instagram_page_group, and the tool name includes 'page_group' but description only mentions 'pages', potentially causing slight ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when to attach a page vs a group or other social accounts). There is no mention of prerequisites, context, or exclusions, leaving the agent without decision support.

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