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

Beyond the annotations, it discloses important behavior: the tool returns a secure link valid for one hour, directs the user to the platform's own login page, and clarifies that Suara never sees the password. It also states that connecting posts nothing and flags the Instagram account-type requirement, all of which materially affect how an agent should use the tool.

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?

Three concise sentences, front-loaded with the usage trigger and followed by the security/return-link behavior and constraints. Every sentence adds actionable information with no filler.

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 one-parameter tool with no output schema, the description covers the trigger, supported platforms, return value (a short-lived secure link), security behavior, and a key prerequisite. Nothing essential for correct invocation is missing.

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 0%, but the single parameter is fully constrained by an enum. The description compensates by enumerating the platforms and specifically clarifying 'Facebook Page' rather than personal Facebook, which adds meaning beyond the raw enum values. A 5 would require more detail about the enum's semantics or side effects.

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 and resource ('connect their Instagram, Facebook Page or TikTok') and explains the downstream purpose (so approved posts can be published). It is clearly distinguishable from siblings like my_social_accounts, which presumably lists existing connections rather than initiating one.

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?

It gives a clear trigger condition: use when the signed-in owner wants to connect an account. It also scopes the supported platforms and notes the Instagram Business/Creator prerequisite. It does not explicitly name alternatives such as my_social_accounts, so it falls just short of a 5.

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