linkedin_add_publication

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

The description only labels the action as 'Add' with no disclosure of side effects, permissions required, or other behavioral traits. With no annotations, the description fails to provide sufficient transparency.

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?

While the description is short, it is underspecified to the point of being unhelpful. It does not earn its place as it adds no value beyond the tool name.

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 lack of output schema, no parameter documentation, and no behavioral context, the description is woefully incomplete for a tool with 6 parameters and many siblings.

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 0% and the description provides no information about any of the 6 parameters, leaving the agent without guidance on how to populate fields like 'url', 'year', or 'description'.

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 the tool adds a publication to a LinkedIn profile, but it is essentially a restatement of the tool name and does not differentiate it from sibling tools like 'linkedin_add_certification' or 'linkedin_add_project'.

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 on when to use this tool versus alternatives. For example, there is no mention of prerequisites or differences from other 'add' tools.

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