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

The SAFETY section clearly discloses the confirmation-gated behavior: nothing goes live until the user opens the confirmation link and ticks accounts, all accounts are unticked by default, and the agent cannot confirm on the user's behalf. This goes well beyond the annotations and is essential for correct invocation.

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 the core operation, then platform rules, then the safety-critical instructions. Although long, every sentence carries necessary operational or safety information, and the structure groups related constraints logically.

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 complex publishing tool with no output schema, the description covers the necessary media constraints, scheduling semantics, return status/confirmation link, and the agent's required user-handoff behavior. There are no obvious gaps that would prevent an agent from invoking it correctly.

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?

Even though schema coverage is 100%, the description adds substantial meaning: media_urls must be public HTTPS, Facebook limits (1-10 images or one video), Instagram media requirements and Reels behavior, caption limits (2200 chars/30 hashtags), and what happens when scheduled_at is omitted. This materially clarifies how to fill the parameters correctly.

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 leads with a specific action ('Publish (or schedule) a post') and names the target resources (Facebook Pages, Instagram Business accounts), and it explicitly separates itself from the sibling 'schedule_post' for LinkedIn. It also details platform-specific post types, so an agent can immediately tell what this tool is for.

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 concrete when-to-use guidance: use it for Facebook/Instagram publishing or scheduling, omit scheduled_at to publish now, pass it to schedule, and route LinkedIn needs to schedule_post with channel_ids instead. The prerequisite to use upload_media/create_upload_link for public HTTPS media is also spelled out.

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