login_jenkins

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

No annotations are provided, so the description carries full burden. It discloses some behavior: opens browser for new users, validates credentials, auto-discovers jobs. However, it does not explain what happens to an existing session, whether it is safe to call repeatedly, or what side effects occur on failure. Significant gaps remain for a login/mutation tool.

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 three short sentences, front-loaded with the main purpose. It includes useful behavioral notes without fluff, though the first sentence 'Login to Jenkins' is somewhat redundant with the tool name.

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 tool has 4 params, no output schema, and no annotations. The description covers purpose and some behavior, but omits return values, error handling, idempotency, and prerequisites (e.g., whether credentials are required). It is adequate but leaves important operational details unanswered.

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 100%, so baseline is 3. The description adds minimal context ('Validates credentials' suggests user/apiToken usage, 'auto-discovers all jobs' implies baseUrl) but does not add meaningful details beyond the schema descriptions.

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 'Login to Jenkins' with a specific verb and resource, and adds context 'Opens browser to Jenkins token page for new users' and 'auto-discovers all jobs', which differentiates it from sibling login_slack and other tools.

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 description implies this tool is used for Jenkins authentication, but does not explicitly state when to use it vs alternatives like whoami or logout, nor does it mention when not to use it (e.g., if already logged in). No exclusions or alternatives are named.

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