add_suites_to_execution

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

The description discloses key behavioral details beyond the annotations: cases are snapshotted at their current state, suites keep their own identity, cross-project suites are skipped, and duplicate suites are skipped rather than snapshotted twice. It also states the return shape, {added, skipped}, which compensates for the lack of an output schema. No contradiction with 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?

Every sentence earns its place. The description front-loads the core behavior, then covers alternatives, edge cases, and return shape without unnecessary filler. It is concise yet information-dense.

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?

Given only two schema-covered parameters, no output schema, and clear annotations, this description is complete enough for an agent to select and invoke the tool correctly. It explains behavior, selection criteria, exceptions, and expected output in a compact form.

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%, and both executionId and suiteIds already have clear schema descriptions. The tool description reinforces the meaning of suiteIds with 'whole Suites' and snapshotting context, but it does not add additional parameter-level detail beyond what the schema already provides.

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 a specific verb and resource: 'Add whole Suites to a Manual Test Execution.' It clearly explains what happens to the cases inside the suites and how suite identity is preserved, making the tool's function obvious. The description also differentiates it from related collection-based and case-based 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?

It explicitly says when to use this tool: 'Pick this when the work is organised by suite.' It also names the alternatives, add_collections_to_execution and add_cases_to_execution, and states the conditions for choosing them instead. This is strong routing guidance with no ambiguity.

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