zabbix_user_login

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

No annotations and the description gives no behavioral details. It does not mention side effects (e.g., token creation), authentication requirements, or what happens upon success/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?

The description is a single sentence, but it is under-specified. Conciseness is not beneficial when key information is missing.

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?

Given many sibling tools related to user management, the description should explain the tool's role (e.g., session creation). It lacks details about return values, even though an output schema exists.

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 schema has one parameter 'params' with 0% description coverage. The description adds no meaning to the parameter, leaving the agent without guidance on required fields or format.

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 states it is the 'Zabbix API user.login method', which clarifies the domain but does not specify the action (e.g., authenticate and return session token). It is slightly better than a tautology but lacks differentiation from siblings like zabbix_user_checkAuthentication.

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 explicit guidance on when to use this tool versus alternatives. It is implied that login is a prerequisite for other API calls, but no usage context, prerequisites, or exclusions are provided.

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