linkedin_add_certification

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

The description only states the action, which matches the annotations (readOnlyHint=false) but adds no additional behavioral context. It does not mention side effects, duplication risks, or authorization requirements, which would complement the openWorldHint and idempotentHint 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?

A single, front-loaded sentence with no filler. It communicates the essential action clearly.

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 tool's moderate complexity and good schema/annotation coverage, the description is minimal but adequate. It lacks usage guidance and any behavioral caveats, but the schema and annotations fill many gaps. Not fully complete but not severely deficient.

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?

Input schema covers 88% of parameters with descriptions, so the schema carries most of the parameter semantics. The description adds no specific parameter-level guidance beyond what the schema already provides, resulting in baseline 3.

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 the specific verb 'Add' and identifies the resource as 'licence or certification' and target 'profile', clearly distinguishing it from sibling add_* tools like linkedin_add_language or linkedin_add_education.

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?

No guidance is provided about when to use this tool versus alternatives. It doesn't mention prerequisites, disambiguation from other add_* tools, or any exclusions.

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