jenkins_get_job

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

No annotations are provided, so the description must fully convey behavioral aspects. It only states what the tool does (get details) without mentioning side effects, access requirements, or any potential impacts. An agent cannot infer safety or idempotency.

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, well-structured sentence that is concise and front-loaded. Every word adds value, though 'details' is somewhat generic. It is efficient but could potentially include more specific output information.

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 no output schema and a low-complexity tool, the description should clarify what 'details' means or list key fields. It is too vague, leaving an agent uncertain about the return structure. Compare to high-quality examples that explicitly mention scope or content.

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% for the single parameter 'job_name', with a clear description. The tool description adds context about folder paths, but does not significantly enhance understanding beyond the schema. Baseline of 3 is appropriate.

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 tool's purpose: getting details of a Jenkins job. It specifies the resource ('job') and action ('get'). It distinguishes from sibling tools like 'jenkins_list_jobs' (which lists jobs) and 'jenkins_get_build' (which gets build details).

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 explains how to use the tool (by name or folder path) but does not provide guidance on when to use it vs. alternatives, or when not to use it. It lacks explicit context for choosing this tool over siblings like 'jenkins_list_jobs'.

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