list_jenkins_actions

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

There are no annotations, so the description carries the full burden. It clearly discloses a read-only listing behavior and specifies what will be returned: each action's name, what it does, and its required parameters. It does not explicitly state 'does not execute actions,' but the verb 'List' makes this evident.

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?

Three short sentences with no filler. The core purpose is front-loaded, the return value is summarized, and the usage guidance is placed at the end as the natural next step. Every sentence earns its place.

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?

For a zero-parameter discovery tool with an output schema, this is complete: it tells the agent what it will receive, why it matters, and when to call it. Sibling tools are operational actions, so the discovery role of this tool is unambiguous.

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?

The tool has zero parameters and the schema has no properties, so the baseline is 4. The description correctly avoids documenting parameters, and its promise to return each action's required parameters reinforces why calling it without arguments is useful.

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?

Uses a specific verb and resource: 'List the Jenkins actions this server can run.' It also describes the return value (action name, purpose, parameters), which clearly differentiates it from sibling tools like run_jenkins_action, get_jenkins_build, and get_jenkins_console.

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?

Explicitly says 'Call this first if you are unsure which action or parameters to use,' giving a clear when-to-use directive. It does not explicitly name sibling alternatives or state when not to use it, but as a discovery tool, the intended usage is clear.

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