commands_bulk_overwrite_guild

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

Beyond the annotations (destructiveHint, idempotentHint), the description reveals critical behavior: any commands not listed are deleted, an empty array deletes every command, the operation is atomic, and it requires __confirm:true combined with MCP_DRY_RUN=false to apply. It also discloses the dry-run preview fallback and the exact return shape. This goes well beyond what annotations provide.

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 tightly structured with bold labels (Purpose, Caution, Security, Returns) and every sentence carries meaningful information. It is compact yet complete, front-loading the core purpose and then layering caution and security details. No filler or redundancy exists.

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 destructive, high-impact bulk operation, the description covers the purpose, safety confirmation, dry-run behavior, and return format. The schema covers all parameters, and the description's caution about confirming scope addresses the main companion tool. Together with annotations, this leaves no significant operational 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?

The input schema already provides 100% coverage for all four parameters, including descriptions for commands, guild_id, __confirm, and application_id. The description adds no new parameter-level detail beyond what the schema states; it only restates the replace semantics already in the schema's commands description. Baseline 3 applies because the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Atomically REPLACE the guild-scoped command registry.' It clearly distinguishes from global bulk overwrite and per-command create/modify/delete siblings by emphasizing the guild scope and wholesale replacement semantics.

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 'Caution' line explicitly instructs to call commands_list_guild first to confirm scope, which is direct guidance for safe usage and names an alternative. It implies when to use this tool (full replacement) but doesn't enumerate all when-not scenarios. This is clear context with one named alternative, short of exhaustive exclusion guidance.

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