linkedin_create_post

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

No annotations are provided, so the description must convey behavioral implications. It states 'Publish' which indicates a mutating action, but does not disclose that the post becomes public, that the action is irreversible, or that there may be rate limits or permissions required. The confirm parameter hints at deliberate action, but the description itself adds no such context.

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 that is front-loaded with the action and resource. Every word earns its place, and there is no redundancy or filler.

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 simplicity of the tool (two parameters, no output schema), the description covers the basic purpose. However, it lacks critical behavioral context such as irreversibility and public visibility, and it does not mention what the tool returns on success or failure. The schema covers parameters but not these operational aspects.

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 the parameters are already well-documented in the schema. The description adds no additional semantic meaning beyond what 'commentary' and 'confirm' already convey. 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 uses the specific verb 'Publish' and clearly identifies the resource as 'a text post to the authenticated member's LinkedIn profile.' It distinguishes itself from sibling tools which are about authentication and profile retrieval.

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 clearly implies the tool is for posting text content to LinkedIn. It does not explicitly state when not to use it or mention alternatives, but among siblings it is the only posting tool, making the usage context clear enough.

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