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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the substantive context behind those flags: it posts publicly on the user's real accounts, cannot be undone, and retries skip platforms already published. That mechanism-level detail about partial-success behavior is not derivable from the annotations and is exactly what an agent needs before an irreversible write.

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 short sentences, front-loaded with the action, then the risk, then the mitigation. No filler, and the most safety-critical clause ("cannot be undone") is placed where it will be read before the call is made.

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 an irreversible write with no output schema, the description covers the essentials: side effects, reversibility, the confirm gate, and retry safety. It does not describe what a partial or total failure looks like in the response, which would help an agent report outcomes, but that is a minor gap given the tool's simplicity.

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 67% (postId undocumented, projectId and confirm documented). The description reinforces confirm's meaning by tying it to the user-approval gate rather than a generic boolean, which is more actionable than the schema's own wording. postId's role is implied by "an existing post" but never explicitly explained.

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 ("Publishes an existing post to its platforms") plus a timing qualifier ("immediately") that cleanly separates it from the sibling schedule_post. An agent can tell at a glance that this is the act-now variant rather than the queued variant.

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 precondition workflow: "always ask the user first, then pass confirm: true," which tells the agent exactly what must happen before invocation. It also notes retry is acceptable because already-published platforms are skipped. What's missing is direct routing advice against siblings (e.g. use schedule_post when the user wants a future time).

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