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

Annotations flag a destructive, open-world write, and the description adds the crucial behavioral detail beyond them: the first call posts nothing and returns a preview plus token, and posting happens only after explicit confirmation. It also discloses platform-specific behavior (dash-separated blocks become a chained X thread), which an agent cannot infer from annotations or schema.

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, front-loaded with the core action, then the required call sequence, then a platform nuance. Every sentence carries actionable information with no restatement of the name or schema.

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 publish tool with no output schema, the description covers the safety-critical elements: what the first call returns (preview + token) instead of posting, the confirmation gate, and the multi-account/thread behavior. Nothing needed to invoke it correctly 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 parameter documentation is already strong, but the description adds the workflow semantics that tie confirmation_token to the two-phase preview/confirm cycle rather than just describing the field in isolation. The dash-thread formatting note adds content-level meaning that the schema does not capture.

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 the target surfaces ('the user's LinkedIn or X account immediately'), which cleanly separates it from siblings like schedule_post, improve_post, and get_post_ideas. An agent can identify the tool's job without opening the 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 two-call protocol: first call without confirmation_token to obtain a preview and token, show the user, then re-call with identical arguments only on agreement. It also names the alternative paths (preview vs. actual publish) and the condition that selects each, leaving nothing to inference.

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