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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower; the description reinforces safety ('Does not change anything') and adds non-obvious field semantics such as rulesSaved=false meaning the channel falls back to Mark's default rules. It does not add auth or rate-limit context, keeping it below a 5.

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 scope and the platform list, then the disambiguation, then a safety note and a Related line. Most sentences carry signal, though the field-mechanics sentence about posting slots is slightly dense and the Related list is somewhat long.

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?

An output schema exists, so the description need not explain return values, but it usefully pre-empts confusion by defining rulesSaved and the connection-vs-integration distinction. For a no-parameter read tool this is complete; little is missing beyond edge-case behavior.

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 correctly focuses on interpreting output fields (rulesSaved, approval mode) rather than inventing parameter semantics.

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 verb and resource (list every social channel Mark publishes to), enumerates the platforms, and describes what each entry carries (connection status, approval mode, active flag). It also names the sibling it is not (list_connections) so an agent can route without opening either 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?

Explicitly says this is where to check whether a social account like a LinkedIn page is connected, and tells the agent that list_connections shows integrations instead, with the reason (all social accounts share one Social publishing row). Both the when and the alternative are stated.

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