xray_search_test_executions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the issuetype filter is applied automatically and warns not to include 'issuetype' or 'ORDER BY' in jql, which is critical for correct usage. It also gives an example, but does not describe pagination or the default return fields beyond what schema notes.

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?

The description is concise and front-loaded with the core purpose, then delivers practical usage details in three sentences. Every sentence provides useful information without repetition or fluff.

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 tool with 5 optional parameters and no output schema, the description covers the main usage contexts well, including filters, sorting, and examples. However, it omits details about default return fields and pagination behavior, which are relevant for a search tool, but the schema provides maxResults bounds.

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 detailed per-parameter descriptions, so baseline is 3. The description adds value by providing a full usage example and emphasizing the automatic issuetype filter, which is not explicit in the schema. This enhances understanding of how parameters work together.

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 states the tool 'Searches for Test Execution issues in Jira using filters,' using a specific verb and resource. It distinguishes itself from siblings like xray_search_test_plans (which searches test plans) and xray_get_test_execution (which retrieves a specific execution).

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 clear usage context with concrete examples for projectKey, jql, and orderBy, and explains how filters combine. However, it does not explicitly contrast this with alternatives (e.g., when to use xray_get_test_execution instead), so it lacks explicit when-not-to-use guidance.

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