add_collections_to_execution

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

Annotations carry no behavioral signal beyond non-read-only, but the description discloses key behaviors: snapshots collections and keeps identity, skips collections from another project, skips shadow collections, skips duplicates instead of double-snapshotting, and returns {added, skipped}. This fully covers likely agent concerns.

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 yet information-dense; every sentence adds value. The main purpose and selection guidance are front-loaded, and the edge-case behaviors are summarized compactly at the end.

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?

Despite lacking an output schema, the description states the return shape {added, skipped}, covers selection guidance, explains snapshot identity, and enumerates all skip cases. It gives an agent everything needed to invoke this tool successfully and predict results.

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 schema already documents both parameters with descriptions and 100% coverage, so the baseline is 3. The description adds contextual meaning about collections being snapshotted but does not add new per-parameter syntax or format details 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 specific verb and resource ('Add whole Test Collections to a Manual Test Execution') and clearly distinguishes it from sibling tools by contrasting snapshotting whole collections with adding suite cases or loose cases.

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?

It explicitly provides the selection cue: 'Pick this when the work is already gathered into a Collection.' It also names alternatives add_suites_to_execution and add_cases_to_execution with their conditions, so an agent can choose correctly.

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