confluence_delete_blog_post

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

With no annotations, the description bears full burden. It discloses two distinct behaviors: default moving to trash and permanent deletion via purge=true. Also notes that purge only works on trashed posts. Missing prerequisites (e.g., permissions) or reversibility of trash, but for a delete tool, key behaviors are covered.

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?

Single sentence that front-loads the purpose 'Delete a blog post.' immediately followed by key behavioral details. No unnecessary words, every part adds value.

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 tool with 3 fully described parameters and no output schema, the description covers the core behavior adequately. It could mention return value or prerequisites (permissions), but the essential information for correct invocation is present.

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% with descriptions for all parameters. The description adds context by explaining the relationship between default behavior and purge parameter, and clarifies the restriction on purge. This adds meaning beyond the raw schema.

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?

Description clearly states 'Delete a blog post' with verb and resource. Distinguishes from sibling tools like delete_page by specifying blog post. Provides immediate clarity on the action.

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 explains when to use default vs purge: 'use purge=true to permanently delete' and notes it only works on trashed posts. Does not explicitly list when not to use the tool, but context of purge is clear. No alternative tools suggested, but the name itself differentiates from delete_page and delete_space.

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