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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is real: 'Permanently... Irreversible' plus a confirm-first instruction and the platform-side persistence caveat. It still doesn't describe what happens on an invalid/repeated uid or the response shape, keeping it just short of top marks.

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?

Three tight sentences with the destructive scope front-loaded, the identifier source next, and the platform-side boundary last. No redundancy against the schema or title.

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 single-parameter destructive tool with no output schema, the description covers purpose, argument source, irreversibility, user confirmation, and the caveat about the social platform. Nothing material an agent needs before calling is missing.

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?

Only one parameter and schema coverage is 100%, so the schema already documents post_uid. The description's 'uid from list_posts' mirrors the schema and adds no format or edge-case detail beyond it, so the baseline 3 applies.

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 (permanently delete) and resource (a post from Feedlio) with the source of the identifier (uid from list_posts). It also clarifies the boundary of the operation ('does not remove content already published on the social platform'), which makes it distinguishable from cancel_post and update_post.

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?

Gives clear context for how to obtain the argument and an explicit confirm-with-user prerequisite before calling. It does not, however, explicitly contrast with the sibling cancel_post, leaving the delete-vs-cancel decision to inference.

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