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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds real value beyond that: it discloses the returned fields (handle, connection date, progress-post eligibility, Pro status) and a security guarantee that no keys or passwords are exposed.

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?

A single densely-packed sentence with no waste, and the payload contents are front-loaded. The parenthetical phrasing is slightly compressed but not unclear.

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?

With no output schema and no annotations about return shape, the description carries the burden of explaining what comes back, and it does so concretely. It stops short of noting ordering or volume, which for an unfiltered per-user list is a minor gap.

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 there is nothing to disambiguate; baseline is 4. The description correctly describes an unfiltered listing with no mention of arguments.

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?

States a specific resource (connected social networks) and enumerates the fields returned, so an agent knows exactly what this tool yields. It is implicitly distinguishable from add_social_account/delete_social_account by the list-vs-mutate verb, but never names those siblings explicitly.

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 implied by the verb 'list' and by the sibling set containing add/delete_social_account, so an agent can infer when to call it. However, there is no explicit when-to-use statement or routing to an alternative.

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