discord_export_snapshot

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

No annotations are provided, so the description must carry the burden. It lists what is exported, which is useful, but it does not clarify that the operation is read-only, describe the return format, or mention that includeMembers can add a member list. The phrase 'for planning or backup' hints at a snapshot behavior but is not fully explicit.

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 a single, front-loaded sentence that covers the main purpose and content without wasting words. It is concise and well-structured.

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 there is no output schema and no annotations, the description should provide more detail about what the export includes and how parameters affect the result. It covers the main scope but omits the optional member inclusion and limit behavior, leaving gaps for the agent.

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 0%, so the description must compensate by explaining parameters. It does not mention guildId, memberLimit, or includeMembers. The parameter names give some hints, but the description adds no additional meaning, and memberLimit's effect on output is unclear.

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 uses a specific verb 'Export' and clearly lists the resources included (guild metadata, roles, channels, AutoMod, onboarding, welcome screen). This distinguishes it from sibling tools like discord_get_guild, discord_onboarding, and discord_welcome_screen, which target individual areas.

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 provides clear context by stating the tool is 'for planning or backup', which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, such as 'for individual components use discord_get_guild or discord_onboarding'.

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