add_cases_to_execution

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

The annotations only provide basic readOnly/destructive hints, so the description adds meaningful behavioral context: it creates a named group, returns groupId, skips cases from other projects, and does not create a group when the result is empty. This goes well beyond the schema and gives the agent a clear model of side effects.

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 front-loaded with the core purpose and every sentence adds value: sibling differentiation, numeric ID clarification, alternative routing, and edge-case behavior. No filler or repetition of schema details.

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?

With no output schema present, the description properly states the return shape as {added, skipped, groupId}. All three required parameters are semantically covered, sibling alternatives are addressed, and important non-obvious behaviors are disclosed. This is a complete description for an agent to invoke the tool 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?

The schema already covers all three parameters, but the description adds important nuance beyond the schema: caseIds are numeric IDs and 'never TC-numbers', and name is required because loose cases have no identity of their own. It does not add detail about executionId beyond what the schema says, but the added semantic guidance is substantive.

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 individual test cases to a Manual Test Execution as a new named group') and clearly differentiates this tool from add_suites_to_execution and add_collections_to_execution by explaining the distinction between loose cases and gathered suites/collections. An agent can immediately tell what this tool is for relative to its siblings.

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?

Explicitly names alternatives and the conditions under which they should be used: 'Use add_suites_to_execution or add_collections_to_execution when the cases are already gathered into one of those.' It also clarifies an edge case behavior ('empty result creates no group'), helping the agent decide whether this is the right tool.

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