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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the shape of the result (which fields and support flags appear), which is content not behavior and largely duplicated by the output schema.

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?

Two sentences, no filler: the first defines the result set, the second states how to use it. The most useful information (what you get) is front-loaded.

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 tool with a full annotation profile and an output schema, nothing necessary is missing. The description supplies the workflow link to connections.add, which the structured fields cannot express.

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 baseline of 4 applies. The identifiers mentioned (network_id, network_type_id) belong to the downstream connections.add call, not to this tool's own schema, so no parameter semantics need explaining here.

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?

Names a specific verb and resource ('Returns the social networks that can be connected to Blog2Social') and enumerates the returned fields (network name, URL, network_id, profile/page/group support). It also names the sibling it feeds into (connections.add), so an agent can distinguish it from connections.list and networks.list_properties.

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?

Explicitly states the workflow: take network_id plus a supported network_type_id and pass them to connections.add. That is clear context and a named alternative, but there is no when-not guidance (e.g., when to use networks.list_properties instead of this tool).

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