jenkins_create_view

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

No annotations are provided, so the description carries the full burden. It does disclose the view_type options ('list' default or 'my') which is useful behavioral context. However, it doesn't explain what happens for invalid view names, whether creation fails if view already exists, or any permission requirements.

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 efficiently structured with a brief one-line summary followed by a concise Arg list. Three sentences total for three parameters. No wasted words, though view_type could mention that 'my' means 'My View' aliasing is redundant with the parenthetical.

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 is relatively simple with only 3 params and 1 required. It has an output schema so return values need not be described. The view_type options and session usage are covered. Given the low complexity and output schema presence, the description is reasonably complete, though it could note the need for an active session/connection first.

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%, so the description must compensate. It does explain view_name and view_type reasonably well, including the 'list'/'my' options and default. session_name is described only as 'Jenkins session to use' which adds minimal value over the schema. The param descriptions are adequate but not deep.

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?

Description clearly states 'Create a new Jenkins view' with a specific verb and resource. It distinguishes from siblings like jenkins_list_views and jenkins_delete_view, though it doesn't explicitly name them as alternatives.

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 usage (creating views) but provides no guidance on when to use this vs alternatives, no prerequisites (like requiring an active session via jenkins_connect), and no exclusions. The session_name parameter hints at the session requirement but isn't explained.

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