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

Annotations already declare non-destructive and non-idempotent, and the description adds real value on top: the copy is a draft and not queued anywhere, media is carried over with format preserved, scheduled_at=now publishes within a minute, and the call is free. The one omission is what state the new post is returned in, but behaviorally this is well disclosed.

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?

Three compact sentences that front-load the what, then the branching case, then the downstream workflow. The parentheticals ('the media included', 'the format follows unless you name one') carry real information rather than padding, though the final 'queue_post_and...'+'Free.' fragment is slightly clipped.

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 9-parameter mutation with no output schema, the description covers the workflow and side effects well but never says how the agent obtains the new duplicate's post_id, which is the essential hand-off to queue_post_for_publishing. That missing return-value clue leaves a real gap for the tool's main use case.

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 56% schema coverage the description usefully explains the platform/format interaction ('the format follows unless you name one') and gives concrete meaning to caption ('copy written for that network — e.g. a short caption under 280 characters for X'). cta, hook, hashtags and user_goal get no mention beyond their schema entries, so coverage is good but not complete.

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 — copy one post on the calendar — and immediately scopes it with 'its media included (a video post stays a video post)'. That distinguishes it cleanly from update_social_post, schedule_social_post and attach_library_media_to_post without requiring the agent to open any 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?

Gives a concrete trigger for the cross-network case ('To repost it on another network, pass platform') and names queue_post_for_publishing as the follow-up that actually publishes. It does not state when to prefer update_social_post or reschedule_social_post over duplicating, so the sibling boundary is incomplete, but the primary usage path is clear.

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