run_system_tests

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

With no annotations provided, the description carries the full behavioral burden, but it only states the action without disclosing side effects, runtime expectations, whether the system is modified, or how results are delivered. This is a significant transparency gap for a tool that executes a full test suite.

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 a single direct sentence with no wasted words. It front-loads the action and resource, and every phrase adds meaningful scope information.

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 trigger tool, an agent can understand what to invoke, but the description is the sole information source since there are no annotations or output schema. It omits expected return behavior, blocking/asynchronous nature, and potential side effects, leaving clear gaps for predicting the tool's outcome.

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 input schema already fully documents that with an empty object and additionalProperties: false. Parameter semantics are therefore complete by construction, so the description does not need to add parameter details.

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 ('Run') and a precise resource ('the full Textile system diagnostic unit, integration, and E2E test suite'), clearly stating scope and test categories. It differentiates itself from the generic sibling 'run_command' by naming the exact Textile system suite it executes.

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?

There is no guidance on when to use this tool versus alternatives such as run_command, nor any mention of prerequisites or expected conditions. The name implies its use, but the description leaves the selection decision entirely to the agent.

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