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

No annotations are provided, so the description carries the full burden. It discloses that execution happens on an isolated runner and that output is bounded, which is useful safety context. However, it does not explain potential side effects, secret access, or how timeout and working directory behave.

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 two focused sentences with no filler. It front-loads the core action and includes the most important contextual instruction about linking build_id.

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 output schema exists, so return-value documentation is not needed. The description covers the tool's purpose and required build_id linkage, but the 0% schema coverage and absence of annotations leave optional parameters and side-effect behavior under-specified.

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%, so the description must compensate for missing parameter documentation. It gives meaning to build_id and command, but says nothing about shell, runner_id, timeout_seconds, or working_directory, leaving those parameters under-explained beyond their schema names and defaults.

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 specific action—execute a diagnostic command on an isolated CI runner—and clearly defines the output as bounded stdout and stderr. It is clear about the resource and purpose, though it does not explicitly contrast itself with sibling tools like ci_read_build_logs.

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 gives clear context: use it for build troubleshooting and pass the build_id returned by incident tools to keep the investigation linked. It does not list when-not-to-use or alternatives, but the intended usage is unmistakable.

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