Delete Image Post

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral detail beyond that: the operation mutates community state and is gated behind an explicit confirm=true flag, which tells the agent a confirmation step is required before the destructive action fires.

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 with zero filler, and the destructive/mutation warning plus the confirm gate are front-loaded immediately after the tool name. Every clause carries information.

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 mutation with rich annotations and a fully documented schema, the description covers the key agent-facing facts: it changes community state and requires explicit confirmation. It stops short of saying what else is removed along with the image post (comments, reactions) or whether the deletion is recoverable, which would be the final useful detail.

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 100%, with account, confirm, post_id and space_id all documented in the schema, so the baseline is 3. The description restates the confirm requirement but adds no syntax, format, or default information beyond what the schema already provides.

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 verb and resource ("Delete Image Post"), so the agent knows exactly what operation is performed. It does not, however, distinguish this from the closely related sibling delete_post, leaving the image-post-vs-post boundary for the agent to infer.

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 line about confirm=true being for "the user-requested action" implies when the tool is appropriate, and it is reinforced by the schema note to set confirm true only when the user asked for exactly this action. But there is no explicit when-to-use guidance and no mention of alternatives such as delete_post, so usage is only implied.

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