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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered structurally. The description still adds real value: immediate publication, irreversibility, the auto-derived workspace, and the non-obvious caveat that an X retweet does not reappear in list_posts or analytics — behavior no annotation could convey.

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?

Four tight sentences: operation, input provenance, platform scope, cardinality/workspace behavior, then the irreversibility warning last. The irreversibility caveat is deliberately placed at the end where it is most salient, and nothing is repeated.

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 mutation tool with no output schema and full schema coverage, the description covers what is needed to call it correctly and what the side effects are. The remaining gap is the return value (repost ID, per-platform status) and failure behavior for an already-reposted post, which the agent must discover empirically.

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?

Schema coverage is 100%, and the schema itself documents the platform-specific ID formats and the workspaceId constraint, so the schema carries the burden. The description contributes provenance ('postId comes from list_posts', 'accountId from list_accounts') and confirms workspace auto-derivation, which is useful but echoes the schema's workspaceId wording.

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 — 'Repost (reshare) an existing post to the connected account's own feed' — which unambiguously separates it from publish_post, schedule_post, and create_carousel. The platform coverage sentence further pins down the exact operation on each network.

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?

Gives concrete sourcing guidance (postId from list_posts, accountId from list_accounts) and the cardinality rule 'one account reposts one post per call', so an agent knows how to prepare inputs. It does not explicitly contrast with publish_post or schedule_post for the case where the agent wants the post on other feeds, and no when-not-to-use condition is stated.

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