Batch operations

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

The description adds key behaviors beyond annotations: fail-forward, per-operation warnings, not transactional, and name referencing. Annotations already provide readOnlyHint=false, destructiveHint=false, and openWorldHint=true, which are consistent. The description could be more detailed about warning handling.

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?

Two sentences that immediately convey the core functionality and key distinctions. No redundancy or filler, every sentence earns its place.

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 complexity (nested operations, fail-forward behavior) and the presence of an output schema, the description adequately covers behavioral and relational aspects. It could mention the return value briefly, but the output schema fills that gap.

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 description doesn't need to add much for parameters. It mentions the operation types and name referencing, which adds value beyond the schema, but the baseline of 3 is appropriate given thorough schema documentation.

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 runs an ordered list of create/connect/setParam operations, and explicitly distinguishes it from set_parameters_batch which only sets parameters, making the purpose unambiguous.

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 the fail-forward, non-transactional behavior and contrasts with set_parameters_batch, giving clear context. It also mentions name referencing, but could be more explicit about when not to use this tool (e.g., when transactional guarantees are needed).

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