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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description's 'cancel' to 'abort a running build' is consistent with that, so there is no contradiction. However the annotations apply uniformly to a mixed tool whose list_runs/get_run/get_logs actions are clearly read-only, and the description does not clarify that distinction, nor does it mention permissions, auth, or rate limits.

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?

Two compact sentences: the first front-loads the purpose, the second is a dense action-to-meaning map with zero filler. Every clause 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?

With 15 parameters fully documented in the schema, defined annotations, and no output schema, the description covers the essentials and even notes that get_logs output is grouped by step. It omits only secondary context like pagination behavior and auth requirements.

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 each parameter already documents its action scoping ('For get_logs', 'For dispatch') and the required run_id/workflow_id relationships. The description adds the action vocabulary but no format or syntax detail beyond what the schema provides, making the baseline of 3 appropriate.

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 states a concrete verb+resource ('Trigger and monitor CI workflows') and then enumerates all five actions with their individual meanings, so an agent understands exactly what this tool covers. It is clearly distinguishable from siblings like ci_config, branches, or webhooks.

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?

Each action is mapped to an intent ('dispatch' to start a run, 'cancel' to abort, 'list_runs' for history, 'get_run' for details, 'get_logs' for job output), which is strong when-to-use guidance within the tool. It stops short of naming when NOT to use this tool or pointing to alternatives such as ci_config for configuration.

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