delete_linkedin_publication

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states that a publication is deleted from the user's LinkedIn profile, which conveys the destructive nature. It does not mention irreversibility, permissions, or effects on the public profile, but the basic behavior is unambiguous.

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?

The description is one short, front-loaded sentence with no filler. Every word contributes to conveying the action and target.

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 delete operation, the description plus schema is nearly complete: it identifies the action, resource, and required ID. The main omissions are higher-level usage guidance and behavioral caveats, but the tool is simple enough that an agent can invoke it correctly with the provided information.

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% and the single parameter publicationId is already described as 'The ID of the publication to delete.' The description adds no additional meaning about how to obtain the ID or any format requirements, so the schema carries the weight.

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 names a specific action ('Delete'), a specific resource ('publication'), and its location ('from your LinkedIn profile'). This cleanly distinguishes it from sibling deletion tools for skills, positions, education, certifications, and languages.

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 intended use is implied: use this tool when a publication should be removed from the profile. It does not explicitly state when not to use it or call out add_linkedin_publication as the complementary tool, but the verb makes the use case clear for this simple operation.

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