Delete post

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

Annotations already declare destructive=true and readOnly=false, so the safety profile is known. The description adds important scoping behavior beyond the annotations: published posts are preserved, so the deletion is limited to drafts and scheduled posts. It does not discuss reversibility or side effects, but the key behavioral constraint is disclosed.

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?

A single front-loaded sentence that communicates the action and the important scope exception with no filler. Every phrase earns its place.

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 simple one-parameter deletion tool whose annotations already cover destructiveness, the description supplies the critical business rule that published posts are not deleted. The remaining gap is postId semantics, which is not covered in either schema or description.

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 says nothing about the required postId parameter, such as its format or where to obtain it. The parameter name is self-evident, but the description does not compensate for the missing schema documentation.

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 ('Delete a draft/scheduled post') and immediately distinguishes the target scope from published posts. An agent can tell that this is not a general post-removal tool and that published posts are excluded.

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 clearly establishes the applicable case: draft or scheduled posts can be deleted, while published posts are kept. It does not name an alternative workflow for published posts, but the exclusion is explicit enough to guide use.

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