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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond annotations: scheduling skips approval, auto-placement respects the daily LinkedIn posting limit, and the response includes the resolved scheduledAt. No contradiction with annotations.

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 focused sentences with no filler. The main action is stated first, followed by parameter semantics, response behavior, and a verification pointer. Every sentence adds useful information.

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?

The description covers the core workflow: target state ('draft'), scheduling modes, daily-limit behavior, response content, and a verification step. There is no output schema, so noting the response includes resolved scheduledAt is valuable. Minor edge cases like errors for non-draft posts are not stated, but the verification instruction mitigates that gap.

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 schema covers scheduledAt and autoSchedule at a basic level, and the description adds important semantic details: Unix milliseconds, future-time requirement, autoSchedule as default, and daily-limit awareness. contentPostId has no schema description, but its role is clear from the tool name and required status; the description compensates for most of the coverage gap.

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 ('Schedules'), names the resource ('draft content post'), and states a key behavioral differentiator ('skips approval'). It is clearly distinguishable from sibling tools like approve_content_post, submit_content_for_approval, or unschedule_content_post.

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 explains both invocation modes (exact scheduledAt vs autoSchedule), clarifies autoSchedule is the default when scheduledAt is omitted, and gives a concrete precondition: verify the post is in 'draft' status first using campaignstack_get_content_post. It does not explicitly enumerate when not to use the tool, but the guidance is strong enough for correct selection.

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