linkedin_save_post

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no further behavioral context—no mention of side effects, idempotency, permissions, or reversibility—so it fails to add value beyond the structured annotations.

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 sentence that states the action and purpose without any wasted words. It is appropriately concise for a simple operation.

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?

With only one well-documented parameter and no output schema, the description covers the essential purpose and behavior. It could mention whether saving is idempotent or requires authentication, but for a straightforward bookmark action, the current level of detail is adequate.

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 input schema provides 100% coverage with a detailed parameter description (URN, numeric ID, or URL accepted). The main description merely says 'post' and does not add any semantic nuance, so the baseline of 3 is appropriate.

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 opens with the specific verb 'Bookmark' and names the resource 'a post to the user's saved items', which clearly distinguishes this from sibling saving tools like linkedin_save_job (saves jobs) and linkedin_save_draft (saves drafts). The action and target are 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?

The phrase 'for later reading' implies the intended use case, but the description does not explicitly contrast this with alternatives such as linkedin_save_job or explain when to choose this over other save mechanisms. It provides context but no direct comparison or exclusions.

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