discord_get_guild_features

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so 'Read-only' merely restates structured data. The description does earn credit beyond that by disclosing the exact flag set it inspects and the derived output (which settings are therefore editable), which tells the agent how to interpret the result before calling.

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 core action, then the enumeration, then the call-to-action 'Use this before...' at the end where it is most likely to be read as a directive. The 13-flag list is long but is the substantive content of the tool, so it is mostly earned; the parenthetical could be tightened.

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?

An output schema exists, so the description need not document return shapes, and it wisely sticks to intent and usage. What is slightly missing is whether the bot needs specific permissions or what happens if the bot lacks access (openWorldHint=true), which matters for a call against a live guild.

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?

There is a single parameter with 100% schema coverage, including type, snowflake pattern and a description, so the schema fully documents it. The prose adds nothing about guild_id, so the baseline of 3 applies rather than a higher score.

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 specific verb and resource ('List the server's feature flags') and goes further by naming exactly which flags it covers and what else is returned (active state, editable settings). It is clearly distinguishable from neighbours like discord_get_guild_info or discord_get_guild_settings, which fetch general server metadata rather than the feature-flag gating model.

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?

Explicitly says 'Use this before attempting a setting that may be feature-gated', which gives the agent a concrete trigger condition. It does not name a when-not case or point to an alternative tool for the opposite situation, so it stops short of full 5-level guidance.

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