Get Community Settings

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description confirms it's a read operation and lists return items, but does not disclose permission requirements, rate limits, or behavior when guild is not a community.

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?

Concise and well-structured: first line states purpose, then a bullet list of examples/args, and a return summary. No fluff or redundant information.

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?

No output schema, so description must detail return structure. It only vaguely says 'community settings including channels and features' without specifying field names or types. Missing error cases (e.g., guild not found, community not enabled).

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 descriptions cover both parameters (guild_id and response_format) completely. The function description adds the default value for response_format and clarifies the purpose of markdown vs json, providing marginal extra value.

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 name and description clearly state this tool retrieves community settings for a server, specifying it shows rules channel, updates channel, and other community-related settings. It is distinct from siblings like discord_get_guild or discord_get_onboarding.

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?

No explicit guidance on when to use this over other guild-related tools such as discord_get_guild, discord_get_onboarding, or discord_get_welcome_screen. No prerequisites or limitations are mentioned.

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