Create Taisly Repost

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

No annotations provided, so description carries full burden. Only states basic function, omitting behavioral traits such as authentication requirements, whether it's destructive, if it starts immediately, or if duplicates are prevented. Minimal disclosure beyond action description.

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?

Single sentence of 14 words, front-loaded with action and resource. No redundancy or unnecessary detail. Efficient and to the point.

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?

Tool is simple with two required parameters, but description fails to clarify what 'repost automation' entails, what the outcome is (e.g., return value like repost ID), or how it relates to sibling tools. More context is needed for a complete understanding.

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 100% with descriptions for both parameters ('from' as source platform ID, 'to' as destination platform IDs). Description adds no extra meaning beyond what schema provides, so 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?

Description clearly states action 'Create', resource 'repost automation', and scope 'from one connected account to one or more destination accounts'. Distinguishes from sibling 'taisly_reposts_list' (list) and 'taisly_posts_create' (create posts, not reposts).

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?

Description implies usage for creating repost automations but provides no explicit guidance on when to use this tool versus alternatives like 'taisly_posts_create' or 'taisly_reposts_list'. No when-not or context for selection.

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