set_execution_source_status

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict them. It adds behavioral context by specifying that status is validated against project test_run_status values, listing defaults, and clarifying the write operates on the group level rather than the case level.

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 compact and front-loaded with the core purpose, followed by lookup guidance, status validation details, and a sibling distinction. Every sentence carries useful information with little redundancy.

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 three-parameter write operation with full schema coverage and helpful annotations, the description provides all needed context: what the resource is, where to get the ID, how status is validated, and the critical boundary against the sibling case-level tool. Nothing essential is missing.

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%, so the baseline is 3. The description goes beyond the schema by explaining where to obtain runId (from get_execution sources[].id or get_execution_cases groupId) and what the status values typically are, including project-custom possibilities.

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: 'Set the status of one source group' inside an execution. It clarifies what a source group is and explicitly distinguishes this from setting an individual case's status by naming report_case_result. The agent can tell this apart from the broad sibling set.

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 gives clear when-to-use guidance and deliberately differentiates from the per-case tool: 'This is the GROUP status; use report_case_result for an individual case's status.' It also tells the agent where to fetch the runId and how to confirm valid status values, making the correct use unambiguous.

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