list_discord_servers

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

The description mentions behavior when authentication is missing (returns a Composio Connect Link) but doesn't disclose what the tool returns on success, side effects, or any other behavioral traits. With no annotations, this is insufficient.

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 one sentence but poorly structured, starting with 'Explain how to list' which is awkward. It tries to convey two separate points without clear organization.

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 no output schema and no annotations, the description should fully explain purpose and return value. It only partially covers authentication failure but not success behavior or expected output, leaving the agent uninformed.

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 input schema has no parameters, so description has no burden to explain parameters. The description adds context about authentication, which is tangential but acceptable.

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 says 'Explain how to list', which is ambiguous and seems like a help command rather than the actual listing operation. It doesn't clearly state that the tool performs the listing of servers.

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 guidance on when to use this tool versus siblings like list_discord_channels. It does not mention prerequisites or context of use.

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