komodo_login

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't disclose authentication failure behavior, whether the token expires or needs refreshing, whether credentials are transmitted securely, or rate limits on login attempts.

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?

Front-loaded with the primary action and outcome in the first sentence. Well-organized with Args and Returns sections. Slightly verbose with the Returns section duplicating what the output schema already conveys.

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?

An output schema exists, so explaining return values is not necessary, yet the description does so. For a security-sensitive authentication tool with no annotations, more context on token lifecycle, error behavior, and credential handling would be valuable.

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%, but the description compensates partially by labeling both parameters (username, password) meaningfully. However, it adds no format constraints, credential source guidance, or security handling notes beyond what the names imply.

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 (Login) and resource (Komodo), plus the outcome (obtain authentication token). It is clearly distinguished from all sibling tools, which are CRUD/list operations on servers, builds, deployments, and stacks.

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 use this tool versus alternatives, and no prerequisites. It doesn't state that most other tools likely require the token this tool returns, nor does it warn against calling it repeatedly.

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