update_global_source_elements

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

Despite only readOnlyHint=false in annotations, the description adds critical behavior: dry_run defaults to true, returns per-element diffs, requires explicit user confirmation before applying, and risks data loss if skipped. It also documents merge semantics that go well 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?

Front-loads the purpose, then structures the required workflow in three clear steps. It is somewhat repetitive with repeated confirmation warnings, but the repetition is defensible for a destructive batch update.

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 a batch mutation tool with no output schema, the description supplies the essential operating protocol, safety gates, and merge rules an agent needs to invoke it correctly. Nothing material is missing for correct use.

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, but the description adds meaningful parameter semantics: dry_run default behavior and update-specific merge rules (style/config/specials shallow merge; events/bindings replace). The component hint parameter is not described, but schema covers it.

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?

Starts with a clear verb and resource: 'Batch update multiple elements in one global source.' The word 'batch' and 'multiple' distinguishes it from the singular sibling update_global_source_element.

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?

Provides explicit step-by-step usage for dry_run=true preview, user confirmation, and dry_run=false apply, including strong when-not guidance ('NEVER proceed without explicit user approval'). It does not explicitly compare to the singular alternative, but the batch scope implies the distinction.

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