x_engage_post_task

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

With no annotations, the description carries the full burden but does add real traits: 'deterministic', account switching, screenshots, and a persisted run journal. It stops short of disclosing permission needs, reversibility of the like/repost mutations, or failure behavior for a stateful multi-step tool.

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?

A single front-loaded sentence that lists the composite capabilities without filler or redundancy.

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 4-parameter mutating task with no annotations and no output schema, the description lists features but omits the two things an agent most needs: when to choose it over its many siblings, and the side-effect/auth profile of an operation that switches accounts and performs engagement actions.

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%, so url, account, like, and repost (including their defaults) are already fully documented in the schema. The description's 'optional like/repost actions' and 'account switch' merely restate those fields, adding no syntax or format detail beyond the schema.

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 (run) and resource (engage-post task) and enumerates the composite behaviors: account switch, screenshots, optional like/repost, journal. It implies differentiation from atomic tools like x_like_post by describing itself as a bundled task, but never names a sibling to disambiguate.

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?

There is no guidance on when to use this composite task rather than the atomic x_like_post/x_repost_post or the generic x_switch_account_and_act_task. The reader must infer the intended scenario from the feature list alone.

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