Refresh social networks

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

Discloses permission requirement (social:posts:publish (Glow+)) and return type (refreshed company-only network list). Annotations already include openWorldHint and destructiveHint=false, so description adds context on provider integration. Missing potential latency or failure modes, but adequate.

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, front-loaded with action and specifics ('Re-sync...'), no wasted words. Efficient and clear.

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?

Covers purpose, usage timing, permission, result type. For a zero-parameter tool with annotations, this is fully sufficient.

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?

No parameters; baseline 4 applies. Description adds no param details since none exist, but the absence is acceptable given schema coverage is 100%.

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 clearly states the action ('Re-sync connected company networks'), specifies the provider (Ayrshare + native X/LinkedIn merge), and distinguishes it from sibling tools like list_social_networks by emphasizing refresh behavior.

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 when to call: after connecting a new account or when list_social_networks appears stale. Provides alternatives implicitly by contrasting with listing.

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