linkedin_create_post

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

The description adds critical behavioral context beyond the annotations: immediate, network-visible publication and the need for user confirmation. It also clarifies the single-media-type constraint. These are meaningful insights not covered by readOnlyHint/idempotentHint/destructiveHint.

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 concise and front-loaded with the core purpose. Every sentence provides useful detail—media types, character limit, immediate-publication warning—without redundant or promotional language. It is efficiently structured for quick comprehension.

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?

Despite not having an output schema, the description covers essential behavior (what it does, media types, limits, immediacy, safety). Combined with a rich input schema covering visibility, document title, and video transcoding nuances, the tool is well-specified for an AI agent to invoke correctly.

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?

With 86% schema coverage, the baseline is 3, but the description adds cross-parameter meaning: 'Only one media type per post' and 'a document (PDF/PPT — this is how carousels are made)' explain how parameters relate and why the document option is significant. This adds value beyond the individual parameter descriptions.

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 opening phrase 'Publish a post to the LinkedIn feed' uses a specific verb and resource, clearly distinguishing it from sibling tools like edit_post, delete_post, or save_draft. The scope is further clarified by enumerating supported media types, making the tool's function unambiguous.

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 statement 'This publishes immediately and is visible to the network, so confirm the text with the user first' provides clear contextual guidance on when to use the tool and a caution about its immediacy. It does not explicitly name alternatives like save_draft for deferred publishing, but the implication is strong.

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