create_test_runs

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

The description discloses several important behaviors beyond the annotations: id must be provided per item, type/status are validated against project enumerations, template_id against existing templates, custom_fields keys are validated but enum-typed values are not, and the operation is atomic. This adds substantial value over the sparse annotations.

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 structured with a lead sentence followed by four bullet points covering key validation details. While a bit dense, each sentence provides useful information. It is appropriately sized for the complexity of the tool.

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 description thoroughly covers validation behavior, atomicity, and references related tooling. It is complete given the tool's complexity and the existence of an output schema, which means return-value details are not necessary.

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?

The description adds critical semantics not present in the schema: id is required per item and never auto-generated, type/status validation rules, template_id validation source, and custom_fields validation caveats. This compensates for the nested fields that lack schema descriptions.

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 opens with 'Create 1-50 test runs in one project in one bulk request', specifying the verb, resource, and scope. It clearly distinguishes itself from sibling tools like create_test_records by naming 'test runs' and emphasizing the bulk, single-project nature.

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 context for when to use the tool: bulk creation of 1-50 test runs in one project. It also references list_test_runs(templates=True) as a prerequisite for template validation. However, it does not explicitly state when not to use it or mention alternatives.

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