run_all_automation_tests

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

With no annotations, the description carries the full burden of disclosure. It simply states 'Run all automation tests' without describing side effects, potential duration, failure modes, or whether it modifies project state. This is a broad operation that should warn about resource usage or that it runs everything.

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 short sentence, but it is under-specified rather than concise in a useful way. It wastes the opportunity to convey important context, similar to the 'Process' example, where brevity is not conciseness.

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?

Without annotations, output schema, or parameter details, the description should compensate by explaining what 'all' means, whether results are returned, and if it is safe to run. The existence of sibling tools (e.g., run_automation_test, run_automation_tests_by_category, get_test_results) makes the lack of context particularly problematic.

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 is empty with 100% coverage, so there is nothing for the description to clarify. The baseline of 4 applies because no parameter documentation is needed.

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 the specific verb 'Run' and identifies the resource as 'all automation tests,' which clearly distinguishes it from siblings like run_automation_test (single) and run_automation_tests_by_category (categorized). The word 'all' conveys broad scope, though it could be more explicit about whether it covers every test in the project.

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?

No guidance is provided on when to use this tool versus alternatives such as run_automation_test or run_automation_tests_by_category. There is no mention of prerequisites, filtering, or exclusions, leaving the agent to infer usage from the names alone.

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