create_test_cases_bulk

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

With no annotations, the description carries full burden. It discloses the POST method, return shape, and important constraints (folder existence, case sensitivity, owner format). It does not cover potential partial failures, rate limits, or authentication, but the given constraints are sufficient for an agent to understand side effects.

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?

Three sentences: functional purpose, projectKey fallback, constraints and return format. Every sentence is meaningfully distinct and front-loaded. No redundant or verbose phrasing.

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?

The tool has 2 parameters (one required), nested items, and no output schema. The description covers the return structure, key parameter behavior (projectKey), and constraints. It references create_test_case for per-field details, which is acceptable given the complexity. Some missing details (e.g., id handling in steps during creation) are minor.

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%, baseline 3. The description adds value by explaining the projectKey fallback logic, referencing create_test_case for field details, and reiterating constraints (folders must exist, case-sensitivity, owner format). This goes beyond the raw 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?

Description clearly states 'Create multiple Zephyr Scale test cases in one call' using a specific HTTP method and endpoint, immediately differentiating it from the single create_test_case sibling. It also specifies the return format as an array of key-url objects.

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?

Provides explicit guidance on projectKey fallback (shared parameter, then ZEPHYR_DEFAULT_PROJECT_KEY) and enumerates key constraints (folders must exist, case-sensitive status/priority, owner format). It does not explicitly state when not to use (e.g., for single test case, prefer create_test_case), but the context of bulk operation is clear.

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