delete_scheduled_post

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

Goes well beyond the annotations (destructiveHint, idempotentHint): it discloses that deleting a published post only removes LazyRelay's record while the post stays live on the platform, and that a post mid-publish cannot be deleted and should be retried. This is exactly the kind of consequence-level context annotations cannot convey.

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?

Four sentences, each earning its place: purpose, primary use, published-post caveat, and the in-flight failure mode. The main use case is front-loaded with no filler.

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 one-parameter destructive tool with no output schema and annotations covering the safety profile, the description supplies all needed context: what gets deleted, when it silently doesn't, and the retry case.

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?

Schema coverage is 100% for the single 'id' parameter and the schema already documents its origin ('from list_scheduled_posts'). The description adds no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Delete a post from LazyRelay') and immediately frames the primary use case (cancel a pending/waiting-for-approval post), which distinguishes it from siblings like pause_post or update_post. An agent can identify the operation 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?

Explicitly says when to use it ('cancel a pending or waiting-for-approval post before it goes out') and covers the edge case of an already-published post. It does not, however, compare itself to alternatives such as pause_post or reschedule_post, so an agent must infer when deletion beats pausing.

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