create_post

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

No annotations are present, so the description carries the full behavioral burden. It clearly indicates a mutation by saying 'Publish', but it does not disclose that the post may become publicly visible, whether the action is irreversible, or any rate limits or failure modes. This is thin for a tool that posts content on the user's behalf.

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 compact and front-loaded: one clear action sentence followed by a one-item Args block. There is no filler, repetition, or extraneous detail.

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 tool is simple with a single required parameter, and the core action is clear. However, with no output schema and no annotations, the missing auth prerequisite and lack of post-publish behavioral detail leave meaningful gaps for a public-facing write operation.

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 must compensate. It adds value by explaining that 'text' is 'the full text of the post to publish,' going beyond the schema's bare 'Text' title. However, it provides no constraints such as maximum length, formatting, or handling of empty strings.

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 concrete verb, 'Publish', and names the exact target resource: 'a post to the authenticated user's LinkedIn feed.' It is unambiguous and easily distinguished from sibling tools that handle auth, profile edits, job search, and applications.

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 gives no guidance on when to use this tool versus alternatives, and does not mention prerequisites such as having an active authenticated session before posting. The appropriate context is only weakly implied by the phrase 'authenticated user.'

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