Delete Blogpost

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

Annotations already declare destructiveHint=true, but the description adds valuable context by explaining that deletion moves to trash by default and can be permanently purged with purge=True. This exceeds the annotation baseline by clarifying the destructive behavior and the reversible/irreversible distinction.

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 two short, front-loaded sentences plus a compact argument list. Every word earns its place; no fluff or redundancy. The structure is easy to scan and immediately conveys the core behavior.

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 delete operation with two parameters and no output schema, the description is complete. It specifies the default behavior (trash), the purge option, and the required ID. No critical information is missing for an agent to invoke the tool correctly.

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 description coverage is 0%, so the description carries the full burden. It clearly explains both parameters: blogpost_id is the ID of the post to delete, and purge controls whether deletion is permanent. This adds meaning beyond the schema's bare names and types.

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' with a clear resource 'blog post', and immediately clarifies the two modes (moves to trash or purges). This distinguishes it from sibling tools like delete_page or delete_comment by explicitly targeting blog 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 description provides clear context about the tool's use through the resource name and the trash/purge distinction, but does not explicitly name alternatives or state when to use this tool over delete_page. The resource-specific nature implies usage, but no explicit exclusions are given.

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