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

Annotations already cover the read-only, idempotent, safe profile, so the bar is low, and the description still adds real substance: the enabled flag's meaning, the fact that non-enabled networks are blocked on vendor app review, and that Telegram/Discord/Slack can bypass review with a business-owned bot or webhook. That is operational context an agent could not get from annotations. Only the return shape/pagination handling remains unstated, and there is no output schema here.

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 core statement is front-loaded, which is good, but the rest is one long clause chain with nested parentheses ('login (social_connect takes the account's name, and the owner types its password or key on a link; how says which)') that is hard to parse on a single read. Several sentences could be split for scanability without losing content.

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 zero-parameter, read-only list with no output schema, the description covers what matters: the connection-mode taxonomy, the meaning of enabled, the app-review gate, and the own-bot alternative. An agent can decide whether and how to act after calling it.

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?

Zero parameters, so the baseline of 4 applies. The description does not need to explain any input, and it correctly spends its words on the response content instead.

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 opening clause states a specific resource and what it returns: every network Conecto can post to plus how each connects. It tells the agent this is an enumeration of connection methods, not a listing of already-connected channels. It never names the sibling it differs from (social_channels), so an agent must infer the boundary.

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?

Usage is only implied: the description explains the connect types and readiness state, which suggests calling this before social_connect, but never says 'use this first' or 'use social_channels instead for X'. The enabled/app-review explanation does give the agent enough to reason about when a network is actually usable, which lifts it above pure omission.

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