run_post_install_task

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

Annotations already indicate this is not read-only and may affect external systems, and the description adds that it executes a Jenkins/Ansible task on a server. It does not disclose whether execution is asynchronous, how results are returned, or what side effects occur beyond running the task.

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 short and front-loaded, with a helpful example that clarifies intent. The parenthetical 'jenkins/call' adds a minor technical detail that is not essential for an agent selecting or invoking the tool, preventing a perfect score.

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 adequate for identifying the operation and basic inputs, but with no output schema it does not explain what the call returns or whether the task runs asynchronously. The required confirm parameter is visible in the schema, but the description itself does not reinforce this important guardrail.

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 100%, so the schema already documents all parameters. The description mostly restates that the task parameter is an ID or name from list_post_install_tasks and mentions additional parameters, without adding deeper semantics about required confirmation or parameter formats.

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 uses a specific verb and resource: 'Выполнить Jenkins/Ansible-задачу на сервере' (execute a Jenkins/Ansible task on a server). It clearly distinguishes itself from list_post_install_tasks by indicating that the task ID or name comes from that list, so an agent can separate run from list operations.

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 a concrete example use case (installing GPU drivers after OS reinstall) and references list_post_install_tasks as the source of task IDs/names. However, it does not explicitly state when not to use the tool or mention alternatives such as check_task for monitoring task progress.

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