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

Annotations already declare a destructive, open-world write, and the description adds materially: the first call posts nothing, the second requires identical arguments plus a token, and a user-confirmation gate exists. The three-dash thread behavior on X is a non-obvious side effect that no structured field conveys.

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?

Three sentences, zero filler, front-loaded with the action and destination, then the call sequence, then the platform-specific edge case. Every sentence carries distinct operational information.

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 destructive, open-world write with no output schema, the description still covers the confirmation gate, preview-then-commit flow, destination ambiguity across two platforms, and the thread separator. Nothing an agent needs in order to invoke it safely is missing.

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 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the two-phase role of confirmation_token (preview call vs. confirm call, arguments must be identical) and the fact that line-of-three-dashes in content creates an X thread. Only account_id handling is left entirely to the schema and its list_profiles pointer.

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?

States a specific verb and resource (publish a post) plus scope (the user's LinkedIn or X account) and adds the immediacy qualifier that separates it from the sibling schedule_post. An agent can distinguish it from list_posts, improve_post, and schedule_post without opening any schema.

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?

Gives an explicit conditional workflow: call once without confirmation_token to get a preview, show the user the exact content and destination, then call again with the token only on agreement. It also covers the X-specific threading case, so both when-to-call and how-to-sequence are unambiguous.

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