Create LinkedIn post (draft-first)

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

No annotations provided, so the description fully carries the burden. It explicitly lists risks (publishes-content, confirmation required), required OAuth scopes, the need for human approval, and the confirm flag with approvalToken. No contradictions.

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 verbose and repetitive, restating the publishing requirements. It could be condensed into a more structured format, e.g., bullet points.

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 no output schema, the description covers the core workflow adequately. However, it does not specify what the tool returns (e.g., post ID or URL), leaving a gap for agents needing return values.

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 50%, and the description adds context for confirm and approvalToken in the workflow. However, it does not elaborate on the other parameters (text, visibility) beyond the schema, so baseline score 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 title and description clearly state the tool creates LinkedIn posts with a draft-first workflow. It distinguishes itself from siblings by being the only post-creation tool in the list.

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 explains the required configuration (enableOfficialPosting, OAuth) and the two-step process (preview then confirm). It does not explicitly exclude use cases, but as the sole posting tool, differentiation is not necessary.

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