social_media_posting_attach_tiktok_profile

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

The description adds no behavioral detail beyond the annotations. With readOnlyHint=false and destructiveHint=false, the agent knows this is a mutating action, but the description doesn't explain side effects, required permissions, or what 'attach' entails operationally. It merely restates the tool's name.

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—a single phrase with no fluff. However, it under-specifies: it omits usage context and parameter semantics, making it more under-specified than appropriately concise. A balanced description would add a few clarifying sentences without redundancy.

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 tool has 9 parameters, no output schema, and minimal annotations, the description is severely incomplete. It doesn't explain the purpose beyond the verb, doesn't clarify required vs. optional parameters, and doesn't mention any integration steps (e.g., OAuth). An agent cannot correctly infer how to invoke this tool with confidence.

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?

Schema description coverage is only 33% (only accountId, companyId, and locationId have descriptions). The tool description provides no parameter explanations, leaving the 6 undocumented parameters (name, type, avatar, originId, username, verified) completely unexplained. The description does not compensate for the low schema coverage.

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 specific verb ('Attach') and resource ('Tiktok profile'), which clearly distinguishes it from other attach tools in the sibling list (e.g., attach_facebook_page_group). However, it does not specify what the profile is attached to or any broader context, so it misses full differentiation.

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 alternative social media attach tools. It does not mention prerequisites, such as having completed TikTok OAuth, or conditions that would favor this tool over siblings like social_media_posting_attach_twitter_profile.

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