add_suites_to_execution

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

The description gives valuable behavioral details: snapshotting, project filtering, duplicate avoidance, and return shape {added, skipped}. However, it directly contradicts the annotations: the description calls the operation 'Idempotent' while the annotations set idempotentHint=false. This is an annotation contradiction.

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?

Three focused sentences, front-loaded with the core action, and each additional detail adds value: snapshotting, project scoping, idempotency, and the return shape. No wasted words.

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?

Without an output schema it states the return value {added, skipped}, and it explains snapshot behavior, project restrictions, and duplicate handling. The schema covers parameters fully. Only minor failure-mode or error details are absent, but the description is sufficiently complete for invocation.

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 both parameters are already documented with clear UUID descriptions. The description adds execution-level semantics such as snapshotting, project filtering, and duplicate skipping, but does not need to explain the parameters further. Baseline 3 is appropriate.

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?

States a specific verb ('Add') and resource ('Suites ... to an execution'), clarifies that Suites are folders of type suite, and distinguishes the operation from sibling tools like add_cases_to_execution and add_collections_to_execution. The snapshot behavior further makes the purpose unambiguous.

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 useful constraints: suites must belong to the execution's project or they are skipped, and duplicates are skipped. However, it does not explicitly state when to choose this tool over the sibling alternatives, so the usage guidance is more contextual than explicit.

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