discord_list_guilds

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

With no annotations, the description carries the full burden. It discloses that the listing covers all guilds the proxied account has joined and that each entry has an id and name, which establishes a read-only, unfiltered behavior. It says nothing about pagination, rate limits, empty-result behavior, or auth requirements for the proxied account.

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 scope sentence is well front-loaded, but the return shape is stated twice ('Returns a list of all guilds with their IDs and names' followed by 'Returns: JSON array of guild objects with id and name'), which is pure redundancy. That repetition wastes space, especially since an output schema already exists.

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?

For a zero-parameter list tool with an output schema, the description supplies what is needed: the resource, the account scoping, and a rough return shape. Nothing essential is missing, though a note on pagination or empty results would round it out.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No argument-related guidance is needed.

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 (list) and resource (Discord servers/guilds), with the important qualifier that it is scoped to the proxied account's joined guilds. It does not explicitly contrast with siblings such as discord_list_channels, but the resource is distinctive enough that an agent can identify it.

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?

Usage is implied rather than stated: an agent can infer this is the discovery entry point for guild IDs needed by channel-related tools, but the description never says when to call it, when not to, or which sibling to prefer. No prerequisites or alternatives are named.

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