commands_bulk_overwrite_guild

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

The description adds significant behavioral context beyond the annotations: it explains the atomic replace semantics, the empty-array deletion behavior, the confirmation requirement, and the dry-run behavior. The annotations already declare destructiveHint=true and idempotentHint=true, and the description aligns with these while adding the crucial detail about `__confirm:true` and `MCP_DRY_RUN=false`. It doesn't contradict the annotations. Minor deduction because it doesn't explicitly mention rate limits or partial failure behavior, but the added context is strong.

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 well-structured with clear sections (Purpose, Caution, Security, Returns) and front-loads the most critical information about the destructive replace behavior. Every sentence earns its place: the purpose, the caution, the security requirement, and the return format. No wasted words or redundant restating of 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?

The description is complete for a destructive bulk operation. It covers the purpose, the destructive scope, the prerequisite check, the security gating, and the return format. The output schema exists, so the return format description is a helpful addition rather than a necessity. The complexity of this tool (atomic replace, confirmation, dry-run) is fully addressed within the description.

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 100%, so the schema already documents all parameters. The description adds value by explaining the `commands` parameter's replace semantics ('an EMPTY array deletes every command') and the `__confirm` parameter's role in authorizing the destructive operation. It doesn't add syntax details for `application_id` or `guild_id`, but those are already clear from the schema descriptions. This exceeds the baseline 3 for full coverage.

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 specific verb ('REPLACE') and resource ('guild-scoped command registry'), and explicitly distinguishes the behavior from other command tools by noting that commands not in `commands` are deleted. It also clearly differentiates from sibling tools like `commands_create_guild` and `commands_modify_guild` by emphasizing the atomic wholesale replace 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 description explicitly tells the agent when to use this tool ('call `commands_list_guild` first to confirm scope') and provides a caution about the destructive nature. It also names the alternative (`commands_list_guild`) and explains the security gating (`ConfirmRequired`, `MCP_DRY_RUN=false`), giving clear context for when this tool is appropriate versus other command-related tools.

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