panelica_accounts_post_v1_accounts_id_impersonate

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

Annotations already declare readOnlyHint=false and idempotentHint=false; the description adds the required accounts:write scope and explicitly states 'Mutating: changes server state.' That is useful but still does not describe the actual impersonation behavior, such as whether the current session changes, a token is returned, or how it must be undone.

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 compact and structured, with each line carrying a specific fact: route, category, scopes, and mutation flag. There is no filler, though the opening 'Create impersonate' fragment is slightly awkward.

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 an open-body mutating action with no output schema, an agent needs more context about what impersonation means, what the request body should contain, and how the action relates to stop_impersonation. This description is too thin to support correct invocation in a meaningful workflow.

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% for the two parameters, so the baseline is 3. The description itself adds no parameter semantics; the body parameter is only described as an open JSON object with no static schema, and the description does not help fill that gap.

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 names the operation as 'Create impersonate' and includes the full HTTP endpoint POST /v1/accounts/:id/impersonate, so an agent can tell it is a POST action targeting an account. However, it does not explain what impersonation actually does or differentiate it from related account actions like stop_impersonation.

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 is given for when to use this tool versus alternatives. The description mentions required scopes and that it mutates state, but it does not explain the session context, pairing with stop_impersonation, or any preconditions.

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