import_nunit_results

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

The description discloses key side effects: automatically creates test execution and updates test statuses. However, with no annotations, it fails to cover permissions, reversibility, or error behavior. Adds some context beyond the bare schema.

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, well-structured sentence that immediately conveys the tool's purpose and side effects. No extraneous words or repetition.

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 simple tool with one parameter and no output schema, the description covers the essential function and side effects. Lacks details on required permissions or error handling, but meets the minimum for effective use.

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 has 100% description coverage for the single parameter 'nunit_xml'. The description's mention of 'NUnit XML test results' adds minimal meaning beyond the schema's 'NUnit XML results as a string'. 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 clearly identifies the verb 'Import', the resource 'NUnit XML test results', and the target 'Xray'. It distinguishes from similar sibling tools like import_junit_results by specifying the NUnit format.

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 no guidance on when to use this tool versus alternatives (e.g., import_junit_results, import_cucumber_results). It lacks prerequisites, context for selection, or exclusions.

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