linkedin_delete_post

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds value by disclosing that reactions and comments are also deleted and emphasizing irreversibility ('This cannot be undone'), which goes beyond the annotation signals.

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 concise sentences immediately convey the action and consequences, with no redundant or extraneous information. The description is front-loaded with the main action and irreversible impact.

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 simple destructive tool, the description covers the essential behavior and consequences. It lacks an explicit mention of the confirm parameter's requirement, but this is fully documented in the schema. Given no output schema and low parameter count, the description is sufficiently complete.

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 100%, with detailed descriptions for both 'post' (URN, numeric ID, or URL) and 'confirm' (must be true, ask user). The tool description adds no additional parameter semantics beyond the schema, so the baseline of 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?

The description clearly states the action: permanently delete one of your own posts, including reactions and comments. This specific verb+resource combination distinguishes it from sibling delete tools like linkedin_delete_draft and linkedin_delete_notification.

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 description implies usage for deleting one's own LinkedIn posts but does not explicitly state when to use this tool versus alternatives (e.g., edit_post) or provide exclusions. The phrase 'own posts' offers context, but no explicit alternative guidance is given in the description.

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