Set Mitigation Groups

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that the operation is mutating, that it runs as a polled background job with an LLM sufficiency check, that it replaces ALL assignments, and that defense-in-depth controls are tracked but not required. This is substantial behavioral disclosure for a destructive-ish mutation.

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 action and mutation risk, then adds the critical call-get-first guidance, then compactly explains the group logic in bullets. Every sentence and bullet earns its place; nothing is filler or redundant with the schema.

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 annotations, the description covers the essential context: replacement behavior, polling/completion semantics, group logic, and parameter intent. An output schema exists, so return-value explanation is not needed. The only noticeable gap is the completely undocumented server_version parameter, which keeps this from being fully complete.

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 high (83%), so the baseline is 3, but the description adds real meaning beyond the schema: it explains the 'justification' parameter's role in the gate ('state the reasoning, not evidence') and clarifies the defense_in_depth semantics and groups JSON structure. The undocumented server_version parameter is not addressed at all, preventing a 5.

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 precise verb and resource: 'Declaratively set the mitigation-group structure for a control objective.' It clearly distinguishes this from the read-side sibling by explicitly telling the agent to call get_mitigation_groups first to inspect current structure. The replacement semantics and group semantics make the tool's role unmistakable.

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 gives concrete usage context: call get_mitigation_groups first, note that all existing assignments are replaced, and understand the AND/OR/defense-in-depth semantics. It stops short of explicitly naming alternatives or saying when not to use this tool versus other group-setting siblings like set_control_assumption_groups, so it misses the highest bar for exclusions.

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