Xray Import Cucumber Features

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

Annotations already state readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the agent knows this is a non-idempotent write to an open world; the description's 'create or update' is consistent with that. It adds the zip-vs-single-file input dimension but does not explain update matching semantics, what happens to existing scenarios, or permission requirements.

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 states the action, the resulting entities, and the accepted input forms with zero 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?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. For a 7-parameter bulk import with scenario-matching behavior, however, more context on how updates are identified (via source) and which payloads apply to Tests vs Preconditions would be expected.

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 7 parameters (including source, test_info, precondition_info) are already documented inline. The description only echoes the single-file/zip distinction already carried by the feature and zip_base64 schema entries, adding no syntax or format detail beyond that.

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 a specific verb pair (create or update) and resource (Cucumber Tests and Preconditions), plus the accepted input format (.feature single file or zip). It is clearly distinguishable from sibling importers like xray_import_tests_bulk and xray_import_execution_results_json, though it never names those siblings explicitly.

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?

There is no guidance on when to choose this over xray_import_tests_bulk or xray_import_execution_results_*, and no mention of prerequisites such as project permissions. Usage is only implied by the name and the 'Cucumber' scope.

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