import_junit_results

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

Discloses side effects (creates test execution, updates statuses) but no details on error handling, authentication needs, or whether existing results are overwritten. No annotations provided, so description carries full burden.

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 concise sentences with no superfluous information. Each sentence adds value: first states primary action, second clarifies side effects.

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 low complexity (1 param, no output schema, no annotations), the description covers purpose and behavior adequately. Could mention return value (e.g., execution ID) but not essential for selection.

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 coverage is 100% with description 'JUnit XML results as a string'. Description repeats the format but adds no extra semantics beyond the schema.

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?

Clearly states the verb 'Import', the resource 'JUnit XML test results', and the target 'Xray'. Also specifies automatic creation of test execution and status updates, distinguishing from sibling import tools (e.g., import_cucumber_results).

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?

Implied usage through format-specific naming but lacks explicit guidance on when to use this tool vs alternatives (e.g., for other formats) or prerequisites.

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