Delimit Content Publish

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

The description clearly discloses side effects for each content type, including the non-obvious report behavior: COMPOSE + STAGE ONLY, posts nothing to X, and creates no live GitHub Release. This goes far beyond the minimal readOnlyHint/destructiveHint annotations and prevents the agent from assuming all three types actually publish externally.

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?

Structured with clear labeled sections (When to use, When NOT to use, Sibling contrast, Side effects), each sentence adds information. The core action is stated upfront, and the detail is proportionate to the tool's branching behavior.

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 tool with three content types that behave very differently, the description covers when, when not, sibling alternatives, side effects, and the critical report staging caveat. An agent has enough context to invoke it correctly and interpret the outcome.

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 fully documents the single content_type parameter at 100% coverage, so the baseline is 3. The description adds value by mapping each allowed value to its concrete behavior (post, generate+upload, or stage-only), which is meaningful beyond the schema text.

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 ('trigger', 'publish') and names the exact resources: tweet, YouTube video, or report. It also distinguishes itself from the sibling tools delimit_content_schedule and delimit_content_queue by stating this performs a single publish step.

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?

Explicit 'When to use' and 'When NOT to use' sections name the exact conditions and the alternative tools to use instead. The sibling contrast further clarifies the division of labor: schedule reads, queue mutates, this publishes.

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