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

Annotations already declare write, destructive, open-world, and non-idempotent behavior. The description adds useful context beyond that—what is refreshed, token verification, and Telegram-specific live-state reading—but it does not explain why the operation is flagged as destructive or what side effects that entails.

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?

The description is front-loaded with a clear write marker and purpose, then adds parameter details and a Telegram note in a compact form. Every sentence contributes to correct invocation.

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 destructive, open-world write operation with no output schema, the description is adequate for calling the tool but incomplete: it omits the destructive implications, authentication/rate-limit considerations, and expected return or failure 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?

With 0% schema description coverage, the description compensates well: it enumerates the platform values (ig|fb|tw|tt|yt|tg), explains that account_id is the platform-specific account ID, and offers account_uuid as an alternative. It does not cover edge cases such as what happens if both or neither identifier is provided.

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 uses a specific verb and resource: 'Re-sync a connected social account', and immediately clarifies the effect (profile/follower stats refresh and token verification). It is clearly distinct from siblings like list_social_accounts or sync_post_comments, though it does not explicitly name an alternative.

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 implies the use case (re-syncing an already-connected account) but does not say when to choose this over alternatives such as list_social_accounts or get_social_report, nor does it state prerequisites or exclusions.

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