add_linkedin_certification

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

No annotations are provided, so the description carries the full behavioral burden. It only states the action 'add' without disclosing side effects, whether the operation is idempotent, authentication requirements, duplicate handling, or what happens after a successful add. For a mutation tool, this is a significant transparency gap.

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 with zero filler. It efficiently communicates the core action in 7 words, meeting the standard of every word earning its place.

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 tool with 8 parameters, no output schema, and no annotations, the description is minimal. It covers the basic purpose, but omits behavioral context like expected return value, error scenarios, and prerequisites. The 100% parameter schema coverage compensates for missing parameter details, but overall completeness is merely adequate, not comprehensive.

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 description coverage is 100%, so all 8 parameters already have descriptive text in the schema. The description adds no parameter-level meaning beyond the word 'certification', which aligns with the resource, but with full schema coverage a 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 states a specific verb ('Add'), a clear resource ('certification'), and a target ('to your LinkedIn profile'). This clearly distinguishes it from sibling tools like delete_linkedin_certification, add_linkedin_skill, or add_linkedin_education, so an agent can immediately identify its function.

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—when you want to add a certification—but gives no explicit contextual guidance, exclusions, or comparisons to alternatives such as add_linkedin_skill or add_linkedin_education. There is no 'when to use this vs. that' information, leaving the agent to infer the boundary from the resource name alone.

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