jenkins_get_view

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's behavioral disclosure burden is low. The description adds that the tool returns 'details and job list', but does not elaborate on what 'details' entails or any edge cases. With annotations covering safety and idempotency, this is acceptable but minimal.

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?

Single sentence that is front-loaded with the action and result. No extraneous words; every word serves a purpose.

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 is brief and lacks important details such as what 'details' include, the structure of the job list, or any error conditions. No output schema is provided, so more context about the return value would be helpful. Given the tool's simplicity and the presence of annotations, this is incomplete but not severely deficient.

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 coverage is 100% (both parameters have descriptions), so baseline is 3. The description does not add meaning beyond the schema; it does not mention parameters or their usage. Thus, no additional value over schema.

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 retrieves details and job list for a specific Jenkins view, using a specific verb and resource. It implicitly distinguishes from sibling tools like jenkins_list_views which list views, and other getters which target different entities.

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. Does not mention prerequisites, such as the view needing to exist, or when not to use it (e.g., if only a list of views is needed, use jenkins_list_views).

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