delete_post

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the soft-delete semantics and the visibility effect ('invisible to other users'), but says nothing about reversibility, whether the author still sees the post, or required permissions/ownership.

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?

Two short sentences, zero filler, with the soft-delete semantics front-loaded right after the verb so the most surprising fact reads first.

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 two-parameter tool with no output schema this is nearly adequate, but a mutation with no annotations should at least hint at permissions/reversibility. The core effect is covered; the operational prerequisites are not.

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% and both parameters (id, slug) are documented in the schema, so the description adds no parameter-level meaning beyond what is already structured. Baseline 3 applies.

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?

Names a specific verb (hide/soft-delete) and resource (a post) and clarifies an important nuance that the tool name delete_post would otherwise obscure: it is a soft delete, not a permanent one. It does not explicitly contrast with edit_post, but the scope is unambiguous.

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?

The description states what happens but gives no when-to-use guidance, no mention of when a permanent delete would be preferable, and no reference to any sibling tool. The agent must infer usage entirely from the name and the word 'Hide'.

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