Permanently remove a DayBy post by its slug to keep your development progress feed accurate and free of outdated or incorrect entries.
Permanently delete a DayBy post by its slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The post slug to delete |
Changes observed during successful MCP inspections.
v0.3.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It does disclose irreversibility through 'Permanently delete,' which is important for a destructive operation. However, it does not mention whether related resources are affected, whether authorization is required, or what happens after deletion.
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 description is a single, front-loaded sentence with no redundant wording or filler. Every word contributes meaning.
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 delete operation, the description plus schema provides enough information for an agent to invoke the tool correctly. The main missing context is side effects beyond the deletion itself, but the tool's simplicity keeps this from being a major gap.
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 already fully documents the single parameter and its description, so the description adds little beyond restating 'by its slug.' Baseline 3 is appropriate since schema coverage is 100%.
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 ('delete'), a concrete resource ('DayBy post'), and the identifying key ('slug'). It clearly distinguishes this tool from siblings like update_post, publish_post, and list_posts.
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 word 'permanently delete' implies the tool is for removing a post when it is no longer needed, but there is no explicit guidance about when not to use it or which sibling to choose instead. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.