add_collections_to_execution

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

The description explicitly says the operation is idempotent, while the annotations declare idempotentHint: false. This is a direct contradiction. Although the description otherwise adds useful behavioral detail about snapshotting, project-scoped skipping, and the return value, the annotation conflict requires a score of 1 per the rubric.

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 convey the purpose, constraints, idempotency, and return shape with no filler. The description is front-loaded with the primary action and resources, making it highly scannable.

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 mutation tool with no output schema, the description is complete: it specifies what is added, how collections are treated, project eligibility rules, idempotency behavior, and the return object. An agent has enough information to invoke this correctly without needing additional explanation.

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 fully documents both parameters, so the baseline is 3. The description adds value by clarifying that collectionIds are snapshotted as test runs, that collections outside the project are silently skipped, and that already-present collections cause no duplication.

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: adding Test Collections to an execution. It also clarifies what 'Test Collections' means as 'manual runs' and clearly distinguishes this from siblings like add_cases_to_execution and add_suites_to_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?

The description explains when this tool applies: adding one or more collections to an execution, with clear behavior for invalid and duplicate collections. It does not explicitly name alternatives or state 'when not to use this tool', but the semantics are clear enough from the description and sibling names.

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