ads_discord_channel_list

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

With no annotations provided, the description carries the full burden, and 'viewable' is a genuine behavioral disclosure implying results are permission-filtered to what the bot can see. Beyond that it says nothing about pagination, ordering, rate limits, or whether the bot must already be a guild member.

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?

A single well-formed sentence with the scope constraint front-loaded and zero filler. It is efficient, though its brevity is part of why behavioral and parameter gaps exist.

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 one-parameter read tool with no output schema and no annotations, the definition omits how to acquire the guild_id and what the result shape or pagination looks like. Adequate to identify the tool, insufficient to call it confidently in edge cases.

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 description coverage is 0% for the single required guild_id, and the description only indirectly maps it by saying 'in one Discord server' (guild = server). It adds no format detail (snowflake ID), no guidance on how to obtain a guild_id, and no constraint semantics.

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 a specific verb ('List') plus a resource ('channels') scoped to 'one Discord server', and enumerates the channel types returned (text, announcement, forum, thread). This distinguishes it clearly from write-oriented siblings like ads_discord_channel_send, though it does not name any sibling explicitly.

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 only implied: listing channels in a server is inherently a discovery step (e.g., to obtain a channel before ads_discord_channel_send), but the description never states when to use it, when not to, or which sibling it supersedes. No exclusions or preconditions are given.

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