wetrack_impersonate

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

With no annotations, the description must carry behavioral disclosure. It mentions the admin requirement and the exit path, but does not explicitly state that the current admin session is suspended or any side effects (e.g., audit logging, permission changes). For a state-changing operation, more transparency would be beneficial.

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?

Two sentences plus an arg list, front-loading the purpose and the sibling. No wasted words; efficient and well-structured.

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 is adequate for a simple impersonation tool: it states the purpose, the prerequisite, and the way to revert. It doesn't describe return values or error scenarios, but the output schema may cover returns. Given that it's an admin operation, it could be slightly more complete, but it's still functional.

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?

The description explains the target_user_id parameter as 'UUID of the user to impersonate,' adding meaning beyond the schema's bare string type. This fully compensates for the lack of schema descriptions (0% coverage).

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?

Clearly states the verb and resource: 'Start an impersonation session — log in AS another user.' It distinguishes from the sibling wetrack_exit_impersonation by naming the complementary action, making its purpose unambiguous.

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?

Explicitly names the sibling tool wetrack_exit_impersonation for restoring the admin session, and specifies that it is 'Admin only,' providing a clear usage condition. However, it doesn't elaborate on when not to use it beyond the admin restriction.

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