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

With no annotations provided, the description carries the burden of disclosing behavior. It states the tool retrieves an invite link and directory, which is a read operation, but does not mention whether authentication is required, any rate limits, or what the returned directory format is. This is adequate for a simple getter but lacks depth.

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 consists of two sentences that are front-loaded with the core action ('Get the RRG Discord invite link and channel directory') and followed by useful 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?

This is a simple zero-parameter tool with no output schema. The description explains what the tool returns (invite link and channel directory) and why the Discord matters. This is sufficient and complete for the tool's complexity.

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?

The tool has zero parameters, and the schema is trivially complete (100% coverage with no properties). Per the rubric, a baseline of 4 is appropriate when there are no parameters, and the description does not need to explain anything further.

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 clearly states the tool's function: 'Get the RRG Discord invite link and channel directory.' This uses a specific verb (Get) and resource (Discord invite link and directory), and it is distinct from all sibling tools. The '[CONNECT]' prefix is an additional categorization clue.

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 context: the Discord is the hub for agent networking, listing notifications, and commerce alerts. This implies when the tool would be useful, though it does not explicitly mention alternatives or when not to use it. Since no similar sibling tools exist, this is clear enough.

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