Create Taisly Post

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

Without annotations, the description must reveal behavioral traits. It states it publishes or schedules and requires user confirmation, indicating it is a mutation. But it does not describe what happens on success/failure, side effects, or any destructive behavior. The information is adequate but not rich.

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 a single sentence that immediately states the action and precondition. It is concise with zero wasted words, effectively front-loading the core purpose.

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 creation tool with 6 parameters and no output schema, the description lacks information about return values, error handling, or post-creation behavior. It covers the basic precondition but is not fully complete given the complexity. The 100% schema coverage compensates partially, but context is still 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 description coverage is 100%, so each parameter is described in the schema. The tool description only mentions generic terms ('media, destinations, caption, and schedule') that map to parameters but adds no additional semantic value beyond what the schema already provides. Baseline score of 3 is appropriate.

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 description clearly states the verb ('Publish or schedule') and the resource ('video post through Taisly'). It includes the precondition of explicit user confirmation, which distinguishes it from other tools. This is specific and unique among sibling tools like taisly_posts_list and taisly_posts_validate.

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 mentions the prerequisite of explicit user confirmation, implying when to use. However, it does not explicitly state when not to use this tool or provide alternatives like the validation tool (taisly_posts_validate) or listing tool (taisly_posts_list). The guidance is minimal.

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