create_system_account

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

Annotations already indicate this is not read-only, not destructive, and idempotent. The description adds useful context by naming the HTTP endpoint, the form-login mechanism, and the username/password auth inputs. However, it does not explain session side effects, which credentials are required for which action, or behavior when credentials are missing.

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 short, front-loaded with the main purpose, and uses a compact Args block. Every sentence adds useful information: the operation, the endpoint, and parameter semantics. There is no fluff or repetition.

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 covers the parameters well, but it does not clarify conditional requirements: login likely needs username and password, while logout may not. This is a meaningful gap because the schema marks only action as required and makes username/password nullable. The presence of an output schema reduces the need to describe return values, but the action-specific parameter dependencies remain undocumented.

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 description coverage is 0%, so the description carries the full burden of parameter meaning. It explicitly lists all three parameters, gives action its allowed values 'login' and 'logout', and explains username and password as Bazarr credentials. This fully compensates for the schema's lack of detail.

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 clearly states the operation: 'Login or logout from Bazarr UI when using form login.' This is a specific verb plus resource and is distinct from sibling system tools like create_system_settings or create_plex_oauth_logout. It also clarifies that despite the 'create_account' name, the tool does not create accounts.

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?

The phrase 'when using form login' provides clear context for when this tool applies. It does not explicitly name alternatives or exclusions, but the form-login condition is a meaningful usage signal and the action enum is described.

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