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

With no annotations, the description fully carries the behavioral burden and does so thoroughly: soft-delete internals, cancellation of BullMQ jobs and queue rows, non-recoverability via dashboard UI, no effect on already-published platform media, user confirmation required, and rejection of publishing-state posts. No important side effect is left undisclosed.

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 main purpose is front-loaded and every paragraph adds a meaningful constraint or side effect. A few ideas are restated (scheduler-side/not platform-published, and the live-post behavior is repeated twice), so it is slightly more verbose than necessary, but still efficient for a destructive operation with many edge cases.

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 no annotations and no output schema, the description covers the critical operational context: irreversibility, what gets cancelled, what stays live, confirmation, and state restrictions. The only notable gap is how the post should be identified via postId/postName, which leaves a small ambiguity for invocation.

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 has 0% description coverage and the description never mentions postId or postName. It does not clarify whether the two identifiers are alternatives, whether both are expected, or how the tool resolves posts by name. The parameter names are self-explanatory, but the description adds no semantic value beyond them.

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 ('Delete a scheduler-side post') and immediately clarifies scope with 'hidden from all dashboards, won't publish' and 'not platform-published.' This makes the tool's function unambiguous and distinguishes it from publishing/deletion tools for live content.

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 when-not guidance: already-published posts stay live on the platform, and the agent does not delete published media. It also states constraints ('Requires user confirmation', 'Rejects posts in publishing state'). It does not explicitly name alternative tools such as cancel_scheduled_post or bulk_delete_scheduled_posts, so it stops short of a full when-to-use vs alternatives statement.

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