create_test_collection

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

Annotations only convey that the tool is a non-read-only mutation. The description adds value by clarifying that it creates a single manual run, can optionally add test cases, returns the created collection with a count of added tests, and defaults priority to medium when omitted. This is helpful context beyond the 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 tight and front-loaded: it states what the tool does, then the distinction from the sibling, then return behavior and a default. Every sentence earns its place with no redundancy or filler.

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 nine-parameter creation tool with no output schema, the description provides sufficient decision-making context: it distinguishes the object from the execution container, notes optional test-case addition, states the return value, and mentions the default priority. Combined with the rich schema, an agent can decide to use the tool and invoke it correctly.

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 description coverage is 100%, so the schema already documents all nine parameters, including the priority default. The description adds high-level semantic context around the collection being a manual run and the optionality of adding test cases, but it does not significantly improve per-parameter understanding beyond the 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?

The description states a clear verb and resource ('Create a new test collection'), defines what the object represents ('a single manual run'), and explicitly differentiates it from the top-level Executions-page container. This clearly separates it from sibling tools like create_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?

Provides explicit routing guidance: use create_execution for the top-level container, and use add_collections_to_execution to attach this collection to an execution. This tells the agent exactly when to use this tool versus the closely related sibling.

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