delete_post

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

With no annotations, the description carries the burden and discloses critical behavior: deletion is irreversible, confirm=True is mandatory, and lookup by title is not supported. It could add auth or error behavior, but the safety-critical information is present.

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?

Concise and front-loaded: the core action, irreversibility, and confirm requirement appear first, followed by relevant sibling differentiation and target-specification guidance. No filler.

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 destructive tool with no annotations, this covers the essential points: target type, irreversibility, confirmation, and distinction from delete_draft. Minor gaps include failure behavior and session/auth prerequisites, but the output schema exists and return-value explanation is not required.

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 0%, but the description compensates by explaining url_or_log_no as the post URL or log number and clarifying that confirm=True must be set even though the schema defaults it to false. Both parameters receive meaningful semantic context.

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?

States a specific action and resource: deletes a published post. Explicitly distinguishes itself from delete_draft, making the target resource and scope clear.

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?

Clearly differentiates this tool from delete_draft and instructs the agent to pass a URL or log number rather than a title. It stops short of explicitly stating 'use delete_draft for drafts,' but the distinction is strongly implied.

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