import_cucumber_results

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

Discloses creation of test execution and status updates, which is beyond the schema. No annotations are provided, so the description carries full burden. However, it omits details like what prevents duplicate executions or required test case existence.

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, front-loaded with action and outcome. Every word earns its place.

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 one-param import tool, the description is reasonably complete. It covers purpose and side effects, but lacks error conditions or behavior on repeated calls. No output schema, so return value is implicit.

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 a clear description for the single parameter. The tool description adds no additional parameter meaning beyond what the schema provides.

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 'Cucumber JSON test results', and the target 'Xray'. Also describes side effects (creates test execution, updates statuses). Distinguishes from siblings by specifying Cucumber 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?

No explicit guidance on when to use this vs. alternatives. The name implies it's for Cucumber JSON, but there is no mention of prerequisites, limitations, or exclusions.

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