social_media_posting_attach_facebook_page_group

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

The description provides almost no behavioral detail beyond 'attach'. It does not disclose side effects, permissions (e.g., whether Facebook OAuth is required), whether the operation is reversible, or what happens to existing attachments. With no annotations providing meaningful safety context (readOnlyHint=false, but no detail), the description carries the full burden and fails to meet it.

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 extremely concise, but this is under-specification rather than effective conciseness. It consists of a single vague phrase with no structure, no front-loaded key information, and no separation of purpose vs. instructions. Every sentence should earn its place, but here there are no useful sentences at all.

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 tool with 7 parameters, no output schema, and a non-trivial operation (attaching Facebook pages), the description is woefully incomplete. It does not explain what 'attach' results in, what data is required for the type object, any expected result, or error conditions. An agent cannot correctly invoke this tool based on the provided information.

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 adds nothing about the 7 parameters. Schema coverage is only 43% (only accountId and locationId have descriptions), and the description does not clarify the purpose of name, type, avatar, originId, or companyId. The type parameter is an open object with no explanation. Since the description is the primary source of meaning for these undocumented fields and is empty, this is a critical failure.

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 'Attach facebook pages' states a verb and a resource but is ambiguous about the target of the attachment and the context. It doesn't clearly distinguish from sibling tools like 'social_media_posting_attach_instagram_page_group' beyond the explicit 'facebook' keyword, and it does not specify what the attachment is for or how it relates to the account. This is barely more informative than the tool name itself.

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?

There is no guidance on when to use this tool versus the many sibling social media posting tools. No mention of prerequisites like OAuth, no indication of when it is appropriate to attach pages, and no alternatives suggested. An agent has no basis to choose this tool over its siblings.

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