jenkins_list_plugins

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

Annotations are not provided, so the description carries the behavioral burden. It's a read-only listing operation (non-destructive), which is evident from 'List all installed plugins'. It doesn't add context about pagination limits, output volume, or whether it requires an active session beyond the session_name parameter. Adequate but not rich.

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 efficient - a single clear sentence defining the action and output fields, followed by a minimal Args section. No wasted words. It's appropriately sized for a simple listing tool.

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 has an output schema and a single simple parameter. The description covers the core purpose (listing installed plugins with version and status). For a read-only listing operation with an output schema available, the description is reasonably complete. It could mention the installation-path contrast with related tools but isn't critically incomplete.

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?

There is only one parameter (session_name). While the description doesn't detail session_name beyond 'Jenkins session to use', the schema coverage is 0% meaning the description adds the only semantic hint available. The description does mention session_name in the Args section, providing minimal compensation for zero schema coverage.

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 lists all installed Jenkins plugins with version and status (specific verb 'List all installed Jenkins plugins with version and status'). It distinguishes reasonably from sibling 'jenkins_list_available_plugins' by implying installed plugins specifically. However, it doesn't explicitly call out the contrast with available plugins.

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 provides implied usage context through the name and described action (list installed plugins). It doesn't explicitly state when to use this vs jenkins_list_available_plugins vs jenkins_get_plugin_info, which are conceptually related siblings. No exclusions or alternative recommendations provided.

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