gh_data_tree_set_batch

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

Annotations only show readOnlyHint=false. The description adds context that the GH document is paused during assignments and recomputed once, and explains the defer_solve flag. This provides behavioral insight beyond the annotation.

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 two paragraphs, front-loaded with purpose, then explains the key defer_solve behavior. It is efficient but could be slightly tighter; still earns its keep.

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?

Given the tool's complexity (batch assignments with nested schema), the description covers the core behavioral intent and critical performance context. Output schema exists to explain return values, so completeness is adequate.

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 0%, meaning the tool description does not explain parameters. While the schema itself has detailed descriptions for nested objects, the tool description adds little to parameter understanding beyond mentioning defer_solve.

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 clearly states the tool applies many DataTree assignments with a single GH solve, specifying the verb 'Apply' and resource 'DataTree assignments'. It does not explicitly differentiate from sibling tools like 'gh_data_tree_set', but the batch nature is implied.

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 explicitly mentions the critical use case of parameter sweeps, where N independent set calls would trigger N solver runs, and explains when to use the tool to avoid that. It also explains the default defer_solve behavior.

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