run_systest_class

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

Annotations already give destructiveHint=false and openWorldHint=false, and the description adds that execution happens unattended via SysTestConsole.exe and that results are per-method. It does not disclose prerequisites or potential side effects of executing tests, but no contradiction exists.

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?

A single, front-loaded sentence that packs action, target, mechanism, and output without 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 no output schema, 'returning per-method results' is a useful but minimal account of the return value; the optional parameters are fully documented by the schema. The definition is complete enough for invocation, though more output format detail would help.

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 all four parameters are already documented. The description adds no additional parameter-level meaning beyond naming the return style; baseline 3 is 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 uses a specific verb 'Execute', a clear resource 'D365FO unit test class', and a distinctive mechanism 'SysTestConsole.exe (/unattended)'. It also states the output 'per-method results', which separates this from sibling build/analysis tools like build_d365fo_project and run_bp_check.

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 makes it evident this tool is for running unit tests, so its core use case is implied. However, it gives no explicit when-to-use guidance or exclusions relative to sibling tools such as run_bp_check or build_d365fo_project.

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