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

The description thoroughly discloses behavior beyond the annotations: it never publishes by itself, returns 'awaiting_confirmation' plus a confirmation link, all accounts default unticked, and the agent cannot confirm on the user's behalf. This gives the agent a precise mental model of the tool's safety and interaction semantics, which the annotations alone do not provide.

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 action and then systematically explains the confirmation flow and agent obligations. Every sentence earns its place, including the SAFETY block which compresses critical behavioral rules into scannable bullets. Length is justified by the tool's safety-sensitive nature.

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?

Given there is no output schema, the description explicitly states the return status and confirmation link. It also covers all user-facing steps, agent instructions, the default state of accounts, and the limit on agent authority. For a tool with one parameter and this safety profile, nothing essential is missing.

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?

The input schema already documents post_id as 'Post id from list_scheduled_posts' with 100% coverage. The description adds context about the post being in a content plan and attached channels, but it does not elaborate on the post_id parameter itself or its format beyond what the schema states, so it meets the baseline without extra value.

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 opens with a specific verb and resource: 'Ask to publish an existing post in a content plan now' and names the target channels (LinkedIn, Facebook/Instagram). This clearly distinguishes it from scheduling tools and other publish tools, while the phrase 'Ask to' signals the confirmation-based flow that defines this tool.

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?

The description provides rich usage context: it explains the confirmation flow, tells the agent to instruct the user to open the link and tick accounts, and warns against treating 'all accounts' as blanket consent. However, it does not explicitly name sibling tools (e.g., publish_to_channels, schedule_post) or state when to prefer one over the other, so it stops short of full when/when-not guidance.

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