Create Taisly Post

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

Adds genuine behavioral context beyond the annotations: success:true only means Taisly accepted the request, not that platforms published, and the agent must verify per-platform status before reporting success. This clarifies the meaning of a mutation result and the required confirmation gate, which the readOnly/destructive/idempotent hints do not convey.

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 dense sentences, front-loaded with the action and precondition, then the success-semantics caveat and the verification path. Every sentence carries actionable information with no filler.

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?

With no output schema, the description fills the gap by explaining what success:true means and what historyId is for, and it covers the confirmation prerequisite. An agent has everything needed to invoke this mutation correctly and interpret its result.

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 100%, so all six parameters (including video, confirmed, platforms, scheduled) are already documented in the schema. The description reinforces the confirmation requirement and references historyId, but adds little parameter-level detail beyond the structured fields, so the baseline 3 applies.

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 ('publishing or schedule a video post') with the precondition 'after explicit user confirmation', so the agent knows exactly what action this performs. It routes the agent to taisly_posts_status for follow-up, but does not explicitly distinguish itself from taisly_reposts_create, the other create-style sibling.

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 a clear usage condition ('after explicit user confirmation') and a concrete workflow for immediate posts (use the returned historyId with taisly_posts_status). It does not spell out when-not-to-use or contrast with taisly_posts_validate, so it falls short of full alternative routing.

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