discord_compare_structure

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description confirms read-only plus discloses exactly what the diff surfaces (presence deltas, role deltas, permission overwrite deltas). It does not cover behavioral edges the agent would want, such as what happens if guild_id does not match backup.guild_id, or whether required bot intents/permissions affect the comparison. Useful added context, but not complete.

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?

Three short sentences: purpose and scope first, then the safety note, then the usage trigger. Nothing redundant and no filler.

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?

With an output schema present, the description need not explain the diff response shape, and it correctly avoids doing so. For a tool taking a deeply nested backup object, the remaining gap is provenance/validation of that object, which the description leaves implicit.

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 only 50%: guild_id is documented in the schema, but the large nested 'backup' object is undocumented there, and the description only calls it 'a structure backup'. It never states the backup must carry format 'discord-mcp-ultimate/structure-backup@1' (typically produced by discord_export_structure) or whether the passed guild_id must match the backup's guild_id. It adds framing but does not compensate for the coverage gap.

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?

States a precise verb and comparison ('Diff a structure backup against the live server') and enumerates the exact classes of change reported: channels/categories present in one but not the other, roles added or removed, permission overwrites that differ. That is well beyond tautology. It stops short of a 5 because it never differentiates itself from the near-identical sibling discord_architect_compare, leaving the agent to guess which comparison tool to pick.

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?

Gives concrete when-to-use triggers: answering 'what changed since the backup?' and checking drift before restoring. That is clear situational context. No explicit when-not-use case or named alternative (e.g. 'use discord_read_structure to inspect without a backup'), so it falls short of a 5.

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