run_systest_class

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

Annotations indicate readOnlyHint=false but no destructive hint. Description adds the interactive session requirement and headless failure, which is useful. However, it does not disclose any side effects (e.g., whether test results are written somewhere, or if it modifies project files). No contradiction with annotations.

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?

Two sentences total, first states purpose, second states a key constraint. No fluff, highly efficient.

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?

Given the tool runs tests, one expects some indication of output or return value. The description doesn't mention what happens on success/failure, or what the agent should do with the result. Also doesn't mention whether it's a build-time operation. However, for a test runner, the agent might infer. Still, it's incomplete.

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 covers all parameters with meaningful descriptions. The description does not add extra parameter-level detail; it just mentions the executable. Baseline 3 due to high schema coverage.

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?

States specific verb 'Execute' and resource 'D365FO unit test class' with the executable SysTestConsole.exe. Clearly distinguishes from sibling tools like run_bp_check or build_d365fo_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?

Provides a clear constraint: requires interactive console session, fails headless. However, it does not mention when to prefer this over related tools like analyze_code or validate_code, nor conditions under which it should be used versus alternatives.

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