create_test_collection

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

The description discloses important non-obvious behaviors: newly created collections always start at status not_started, no status argument is accepted, priority defaults to 'medium', and priority matching is case-insensitive but stored lowercase. It also states return behavior (created collection with count of added tests) and clarifies the distinction from an execution container. These details go well beyond the minimal annotation hints.

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 information-dense but efficiently organized, front-loading the core purpose and the critical disambiguation from executions. Every sentence adds value, and there is no filler or repetition of schema basics.

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 9-parameter creation tool, the description covers the essential call context: what it returns, how defaults work, what it cannot do, and how it relates to adjacent sibling operations. The absence of an output schema is adequately mitigated by explicitly stating the created collection and added test count.

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?

Though the schema already documents all nine parameters, the description adds meaningful semantic nuance such as the default for priority, the lowercase-only constraint, the fact that collection priority cannot be project-customized, and that caseIds are optional. It does not restate every parameter, but it enriches the most behaviorally important one.

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 identifies the action ('Create a Test Collection') and the resource, and immediately distinguishes it from the top-level Executions-page container ('NOT the top-level Executions-page container - use create_execution'). This makes the tool's purpose unambiguous and separates it from sibling tools.

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 explicitly explains when to use this tool versus create_execution and update_test_collection, including routing to add_collections_to_execution for attaching collections to executions. This gives an agent clear decision guidance with named alternatives.

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