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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the non-obvious consequence that the published content survives — the single most important fact about this mutation and one no annotation conveys. It doesn't state whether the history entry is recoverable, which keeps it from a 5.

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 short sentences with zero filler: action, critical caveat, usage guardrail in that order. Nothing could be removed without losing information an agent needs.

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 one-parameter destructive tool with rich annotations and no output schema, the description covers scope, side effects, and the authorization condition. The only gap is what the tool returns or how to confirm the deletion, a minor omission given the annotation coverage.

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?

The schema has 100% description coverage and already tells the agent the post_id comes from list_posts or get_post, including the UUID format. The description adds no further parameter meaning, 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?

Names a specific verb and resource ('Borra una publicación del historial de PilotControl') and immediately scopes it against the obvious misreading by stating it does not delete from the social networks. That scoping is exactly what separates it from siblings like cancel_post or the publish_* tools, so an agent can pick it without opening schemas.

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 an explicit gate: use it only when the user asked for it on that specific post, which prevents over-eager deletion. It stops short of naming alternatives (e.g. cancel_post for scheduled content or get_post to verify the ID), so the when-not path is implied rather than spelled out.

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