delete_linkedin_position

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that a position will be deleted but does not mention that the deletion is likely permanent, what the effect on the profile is, whether authorization scopes are required, or what happens after success or failure.

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 a single, front-loaded, zero-waste sentence. It states the exact action and target without any filler, which is ideal for a simple deletion tool.

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 tool with one well-described parameter, no nested objects, and no output schema, the description plus schema is largely sufficient for correct invocation. It lacks behavioral nuance such as irreversibility, but the core call context is 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?

The schema has 100% description coverage for the single 'positionId' parameter, so the structured data already fully documents the parameter. The tool description adds no parameter-specific information, but none is needed given the schema coverage.

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 uses a specific verb ('Delete') and a specific resource ('a position from your LinkedIn profile'), making the tool's purpose immediately clear. It is easily distinguished from sibling tools that delete skills, languages, education, or certifications.

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 from the delete action and resource, but the description gives no explicit guidance about when to use this tool versus adding or updating a LinkedIn position. No alternatives or exclusions are mentioned.

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