Create Taisly Repost

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

Annotations indicate readOnlyHint=false (write operation) and openWorldHint=true (potential side effects). The description adds context ('automation' and 'to one or more destination accounts') but does not clarify what the automation entails, when it triggers, or any required preconditions like connection status. It adds some value beyond annotations but lacks depth.

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, well-structured sentence that front-loads the action ('Create a repost automation') and states the resource scope. No unnecessary words or redundant information.

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?

The description omits important details for a creation tool: it does not explain what happens after creation (e.g., whether it triggers immediately, expected response), does not reference sibling tools like taisly_reposts_list for follow-up, and does not mention any authentication or connection prerequisites. Given the absence of an output schema, the description should provide more guidance on the result or next steps.

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%, with both parameters already documented ('Source platform ID' and 'Destination platform IDs.'). The description's mention of 'from one connected account to one or more destination accounts' aligns with but does not add new meaning beyond the schema. Baseline score 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?

The description clearly states 'Create a repost automation' – a specific verb and resource (repost automation) – and distinguishes it from sibling tools like taisly_reposts_list (list reposts) and taisly_posts_create (create posts). It also defines the scope: 'from one connected account to one or more destination accounts.'

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 implies usage for creating repost automations but offers no explicit guidance on when to use this tool versus alternatives such as taisly_posts_create or taisly_reposts_list. No when-not-to-use or prerequisite information is provided.

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