jenkins_create_folder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state whether an active connection/session is required, what happens on name conflicts, whether this is a mutating operation, or what the return value/output schema contains. For a creation tool with zero annotations, this is a notable gap.

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 compact and organized with an Args section listing parameters in a scannable format. It front-loads the core purpose efficiently with no wasted words, though the Args block is marginal value since it mirrors the schema.

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?

With an output schema present but no annotations, and 4 parameters with 0% schema coverage, the description should do more. It doesn't address session requirements, error conditions, naming conventions, or how folder creation relates to the job creation workflow. The description is minimally sufficient for the simple purpose but lacks depth for a tool with no annotation support.

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%, meaning the description must compensate, but it only echoes the parameter names (folder_name, parent_folder, description, session_name) without adding meaning. It clarifies that parent_folder empty means root level, which adds slight value, but doesn't explain formats, session requirements, or constraints on any parameter.

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 'Create a new folder in Jenkins' with a specific verb and resource. It distinguishes from siblings like jenkins_create_job and jenkins_create_view by specifying 'folder' as the resource type, though it doesn't explicitly contrast itself from those siblings.

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?

There is no guidance on when to use this tool versus alternatives like jenkins_create_job or jenkins_list_folder_jobs. The description does not mention prerequisites (e.g., needing an active session) or exclusions.

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