post_now

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

With no annotations, the description carries full disclosure burden; it goes beyond the obvious by revealing a guardrail/chokepoint, that blocked/held posts are never sent, and that the token never touches this machine. It also discloses default-off AI labeling and reply chaining. It falls short only on idempotency and exact failure/return behavior.

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 with its core purpose before behavioral and parameter details. It is slightly dense with jargon ('casserole guardrail at the chokepoint'), but every sentence contributes substantive guidance.

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?

Core invocation is covered, but with no output schema the description should state what the tool returns (e.g., platformPostId for chaining replies), and it leaves idempotencyKey semantics unaddressed. It is adequate for a simple text post but not complete for advanced thread/retry usage.

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 60%, so the description must compensate for text and idempotencyKey, which lack schema descriptions. It adds clarity to aiGenerated (user choice, default off) and inReplyToId (platformPostId chaining), but leaves idempotencyKey completely unexplained and does not mention mediaIds.

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 opening sentence names a specific action ('Post text to X now') with a concrete resource and immediacy, which distinguishes it from scheduling/preview siblings. The rest of the description reinforces it as a direct posting action, not a management or upload tool.

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 parameter-level conditions ('Set aiGenerated only if...', 'Pass inReplyToId...') but never states when to choose post_now over siblings like preview or create_loop, or when not to use it. No exclusions or alternatives are named.

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