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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: the requirement of explicit deletion intent before acting, and the provider quirk that LinkedIn post IDs are preformatted/base64-style. It does not address reversibility or failure/recovery behavior, 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?

Front-loaded with the action and the destructive-intent gate, then the ID rules; every clause is operational rather than filler. Slight redundancy from repeating the schema's post_id text nearly word-for-word costs it a point.

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, no-output-schema, two-parameter tool, the description covers intent gating, ID resolution flow, exclusions, and ID format quirks. Nothing an agent needs to invoke this safely and correctly 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?

Schema description coverage is 100%, so baseline is 3. The description's post_id guidance (exact provider ID, format quirk, how to obtain it, what not to pass) is essentially duplicated verbatim in the schema's own post_id description, and account_id is not mentioned at all, so it adds little beyond the structured field.

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 with a scope qualifier ("Delete an exact supported social post"), so an agent can readily separate it from social_delete_comment or social_update_post. It stops short of explicitly naming the alternative tools, but the purpose is unambiguous.

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 prerequisites (resolve/verify post_id first), the intent gate (explicit deletion intent required), concrete resolver paths (linkedin_search_posts / linkedin_list_user_posts / instagram_list_user_posts -> result.id), and explicit exclusions (never pass post text, author user ID, or URL). This is when-to-use, how-to-get-the-argument, and when-not-to content all in one place.

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