create_post

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

With no annotations, the description carries full weight and discloses key behaviors: daily quota, warm-up, business hours, jitter, and media path limitations. It could further explain quota exceeded behavior or warm-up specifics.

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 sentence efficiently covers purpose, optional media, constraints, and a usage tip, with no redundant words. Information is front-loaded.

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?

The description is adequate for basic use but omits return values (no output schema) and does not elaborate on warm-up or jitter behavior. For a 4-parameter tool, this is a minor gap.

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 coverage is only 25%, but the description adds meaning to text (implied as post content), media_path (optional local file with format/size), and dry_run (preview). It lacks explicit explanation of visibility parameter beyond the schema enum.

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 clearly states 'Publish a new LinkedIn post' with a specific verb and resource, and distinguishes from sibling tools like comment_on_post and delete_post by focusing on original post creation.

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 provides constraints (daily quota, warm-up, business hours, jitter) and suggests using dry_run=true to preview, offering clear usage context. However, it does not explicitly compare to alternatives or state when not to use.

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