Run test suite

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the mutation/scope profile is partly covered. The description adds real value beyond that by naming the return shape and two explicit failure modes (MissingParameterError, ParameterError), but it says nothing about side effects, duration, 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?

The leading sentence is front-loaded and clear, but the body is auto-generated Sphinx boilerplate (:param/:type/:raises) that spends most of its length restating parameter names while leaving the majority of the schema unexplained. It is moderately sized but low-yield.

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 43-parameter, zero-required tool with no output schema, the description covers only a fraction of the inputs and omits any indication of how to select among the many mutually exclusive-looking IDs (sys_id vs suite_sys_id vs test_suite_sys_id). An agent cannot confidently construct a call for this tool from the definition alone.

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 schema has 43 parameters at 0% description coverage, yet the description documents only 6 (test_suite_sys_id, test_suite_name, browser_name, browser_version, os_name, os_version). The remaining 37 fields — data, name, scope, sys_id, suite_sys_id, app_scope_sys_ids, and so on — are undocumented in both the schema and the description, so the description does not compensate for the coverage gap.

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 clear verb+resource ('Run a test suite'), so an agent knows the operation. However, it offers no differentiation from likely siblings such as servicenow_suite_scan or servicenow_combo_suite_scan, and 'based on the provided parameters' is filler that adds nothing.

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 suite_scan, combo_suite_scan, or point_scan, nor any prerequisites or exclusions. The only usage signal is the implicit one from the parameter names.

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