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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior on top: it cannot connect accounts (connect_more does that), posting is enabled per-platform as approvals land, and X is not yet available. A slight redundancy is the closing "Free and read only", which restates the readOnlyHint the agent already has.

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?

Front-loaded with the when-to-use condition and the payload, then alternatives and exclusions. It is on the long side for a no-arg tool, and the parenthetical platform list with "X is coming soon" plus the closing "Free and read only" are the least load-bearing parts.

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?

Output schema exists, and the description still summarizes the returned fields and the per-platform note. With usage triggers, exclusions, downstream consumers and a stated confinement (cannot connect accounts), an agent has everything needed to select and call it 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?

The tool takes zero parameters, so the schema baseline is 4. The description still earns that by explaining where the returned account_id is consumed, which is meaningfully more than the empty schema offers.

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?

Specific verb+resource (list the social accounts connected to RipClip), names the platforms covered, and states what each returned row contains (account_id, platform, name, username, status). It is clearly distinguishable from siblings like get_account_stats or get_post_stats, which it explicitly names.

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?

Gives concrete trigger phrases ("where can I post", "which accounts are linked") plus a downstream-use note that draft_post, plan_posts and update_draft take account_id. It also names the out-of-scope cases and the sibling to use instead (post numbers → get_post_stats, follower counts → get_account_stats).

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