create_post

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

No annotations are provided, so the description carries full behavioral burden. It compensates well by disclosing the at-most-one constraint, hashtag behavior, link preview effects, duplicate-post rejection, and the 150/day cap. These go beyond the schema, which encodes none of these constraints.

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?

Four sentences cover purpose, user-confirmation warning, parameter constraints, and platform limits without waste. Backticked parameter names and bolded IMPORTANT make it scannable and well structured.

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 six-parameter write action with no annotations or schema descriptions, the description provides enough operational detail for correct invocation, and an output schema exists. The only notable gap is the visibility parameter, which the enum conveys but the 'public' claim does not accurately address.

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 has 0% description coverage, so the description must explain parameters. It defines link as URL sharing, image_path as local file upload, link_title/link_description as preview-card enhancers, and text as containing hashtags. However, visibility is not described at all, and the blanket 'public' phrasing is slightly inconsistent with the CONNECTIONS enum option.

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 opens with a specific verb+resource: 'Publish a LinkedIn post as the authenticated user.' It is immediately distinct from sibling tools like delete_post, comment_on_post, and like_post, and clarifies the acting entity.

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?

It gives clear context for when to use: after confirming the final text with the user and warns about public professional content. It also provides parameter usage guidance ('Attach at most one of link or image_path'), though it does not explicitly name sibling alternatives because no sibling performs post creation.

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