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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context: it lists 'every' connected account, implying complete enumeration rather than a filtered subset, and frames access as tied to the authenticated user. This is consistent with annotations and adds value beyond safety flags.

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?

One sentence, no filler, action-first wording. Every word contributes meaning: 'List', 'every', 'connected social account', and 'authenticated user' all add distinct information.

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 listing tool, the description covers the key facts: what is listed, for whom, and that it is the full connected set. It does not describe the response format, but the term 'List' strongly implies an array, and output schema is absent. Minor additional detail about authentication requirements or return structure would push it to full completeness.

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 has zero parameters, so the schema carries no semantic load. The description's mention of the authenticated user appropriately clarifies how result scoping works, which is the only meaningful parameter-like context for this operation.

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?

Uses a specific verb 'List' with a clear resource ('Connected social accounts') and clearly sets user scope ('available to the authenticated user'). This distinguishes it from sibling tools like list_posts or get_account_analytics without needing to open the schema.

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?

Provides no explicit guidance on when to use this tool versus alternatives, and no 'when-not-to-use' or sibling comparisons. The user scope is stated, but the decision boundary between this and related account tools is left unaddressed.

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