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

Annotations already cover read-only/idempotent safety, yet the description adds substantial non-schema behavior: the meaning of `needs_reconnect` (posts will fail until in-app reconnection), that `last_options` seeds a new post's options, that nothing is saved or scheduled, and that connecting only happens in the app. These are exactly the constraints an agent needs to avoid fabricating a scheduled post or attempting a reconnect.

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?

It is front-loaded with what is listed and every clause carries meaning, but the dense single paragraph with stacked parentheticals makes it heavy to parse. Slightly more structure would improve it 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?

Given a read-only, zero-param tool with an output schema, the description still supplies the interpretive layer (status meanings, availability flags, localized messaging rule, side-effect disclaimer) that the schema cannot. Nothing an agent needs to call and interpret it correctly is missing.

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 per the rubric the baseline is 4. The description uses the space to interpret returned fields rather than params, which is appropriate 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?

The description names the exact resource (the TikTok, Instagram, YouTube and X accounts this reader connected) and enumerates precisely what each entry carries (status, last_options, configured, allowed, limit). An agent can distinguish this from siblings like get_account_context or list_posts without opening 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?

It gives handling guidance (explain availability via `message`, prepare caption/time in conversation only, reconnect only in the app), which is useful. But it never states when to call this tool versus alternatives, nor an explicit trigger such as 'call this before composing a post' — usage is implied by the last_options framing.

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