x_follow_profile_task

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

With no annotations, the description carries the full burden. It usefully discloses that the task switches accounts, captures screenshots, and verifies profile state, and 'deterministic' hints at repeatability. However, it omits that following is a mutating/irreversible action, any auth or permission requirements, and what happens on failure.

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 with no filler. It is efficient, though the term 'deterministic' is left unexplained and the enumeration of components is dense rather than prioritized.

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 composite, mutating task with no annotations and no output schema, the description is minimally viable. It conveys the ingredients but not the outcome, failure behavior, or artifacts (screenshots) the caller should expect.

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% and both parameters are documented in the schema (account handle/switcher label, username with/without @). The description adds only the notion that account switching occurs, which is already implied by the account parameter, so 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 ('Run a deterministic follow-profile task') and enumerates distinguishing components: account switching, screenshots, profile-state verification. This separates it from the plain x_follow_profile sibling, though it never names that sibling explicitly.

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?

No guidance on when to pick this over x_follow_profile, x_switch_account_and_act_task, or manually chaining x_switch_account + x_follow_profile. The agent must infer selection criteria from the name alone.

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