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

With no annotations, the description transparently indicates this is an informational retrieval ('Get the invite link and channel directory') rather than a state-changing join operation, despite the tool name. It doesn't cover auth or rate limits, but for a zero-param getter this is adequate.

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?

Two sentences, first is action-oriented and front-loaded, second provides context. No wasted words.

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 tool's simplicity (0 params, no output schema) means the description fully covers its purpose and context; nothing essential is missing.

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?

No parameters exist, and schema coverage is 100% (empty schema), so there is nothing for the description to add; the baseline for 0 params is 4.

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 the verb 'Get' with a specific resource ('RRG Discord invite link and channel directory'), clearly distinguishing this tool from the 45 siblings, none of which cover Discord access.

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?

It implies usage by explaining the Discord's role as a hub for agent networking and alerts, which gives clear context for when to invoke it. Though it doesn't explicitly mention alternatives, the uniqueness of the tool makes this context sufficient.

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