add_linkedin_skill

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, but it only restates the action implied by the tool name. It does not mention whether the skill already exists, how duplicates are handled, whether authentication is needed, or what side effects occur beyond adding the skill.

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, clear sentence with no filler or redundant phrasing. It front-loads the action and object, making it easy to scan and understand instantly.

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?

Given the low complexity—one required parameter, no nested objects, and no output schema—the description plus schema is largely sufficient for an agent to invoke the tool correctly. The main gap is the lack of any behavioral context (e.g., response format, duplicate handling), but the simplicity of the operation keeps this from being a major omission.

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 already documents the only parameter ('name') with full 100% coverage, so the description does not need to repeat it. The description adds no extra semantic detail about the parameter, which matches the baseline for a fully schema-covered simple parameter.

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 ('Add') and a clear resource ('a skill to your LinkedIn profile'), making the tool's purpose immediately obvious. It also distinguishes this tool from siblings like add_linkedin_language or delete_linkedin_skill by naming the exact object being modified.

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 provides no guidance on when to use this tool instead of related tools, nor does it mention any prerequisites or limitations. There is no explicit or implied comparison with alternatives like delete_linkedin_skill or add_linkedin_language.

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