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

With no annotations, the description carries the full behavioral burden and does so well. It discloses that the tool runs in the background and returns immediately, publishes nothing, requires content topics, reads results elsewhere, and returns a skipped status with reason on a same-day second call.

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 important constraints are front-loaded and easy to scan. There is minor waste in the repeated title line and the boilerplate Responses/Content-Type section, but the description is still compact and purposeful.

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 zero-parameter asynchronous tool with no output schema and no annotations, the description supplies everything an agent needs: purpose, non-publishing behavior, asynchronous result retrieval, prerequisite, rate limit, and skipped-status behavior.

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 tool has zero parameters, so parameter semantics are effectively moot and the schema is empty. The baseline for a zero-parameter tool is 4.

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 states a specific verb and resource: drafting LinkedIn posts from saved content topics and voice. It also distinguishes the output from publishing ('Produces drafts only and publishes nothing') and routes result-reading to list_content_drafts, so the agent can identify the tool's role without opening the 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?

It gives clear operating context: saved content topics are required, results are read via list_content_drafts, and the pipeline runs at most once per day. It does not explicitly enumerate when to choose this over run_outreach_pipeline or run_commenting_pipeline, but the content-specific framing makes the intended use clear.

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