run_systest_class

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

The description adds a significant behavioral trait beyond the annotations: the requirement for an interactive console session and failure in headless environments. This is not captured in readOnlyHint or destructiveHint, adding valuable context for the agent.

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 sentences long, front-loads the action, and each sentence contributes essential information. There is no redundancy or filler.

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 description covers the core purpose and a critical operational constraint, but with no output schema, it fails to mention what the tool returns or produces (e.g., test results, exit codes). For a test execution tool, this is a notable gap, though the rest of the context is adequately handled.

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 input schema already provides 100% coverage of all four parameters with clear descriptions. The tool description adds no additional parameter-level semantics, so the baseline score of 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 the specific verb 'Execute' and identifies the resource as 'D365FO unit test class via SysTestConsole.exe', making the tool's purpose unambiguous. This clearly separates it from sibling tools like build_d365fo_project or 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 provides clear usage context by stating it 'Needs an interactive console session' and explicitly warns it 'fails headless', effectively defining when to use it (interactive sessions) and when not to (headless). However, it does not name alternative tools for headless scenarios, so it falls short of a perfect score.

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