ads_discord_guild_list

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

With no annotations at all, the description carries the full disclosure burden. It does add real behavioral context by stating results are limited to bot-installed guilds, which prevents an agent from expecting a global directory. However, it says nothing about pagination despite the limit parameter, ordering, or what a returned guild record contains.

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, no filler. The scoping statement comes first and the disambiguation follows immediately, which is exactly the front-loaded structure an agent needs.

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 simple read-only list operation with no output schema, the definition covers what the tool returns conceptually but leaves out pagination behavior and result shape. Adequate to call, not complete enough to use the limit parameter intelligently.

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% and the single parameter 'limit' (1-200) is never mentioned in the description. The description does not explain that results are capped, what the default cap is, or how to page through more than 200 guilds, so the only parameter is documented solely by its schema type bounds.

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'), scoped to where the configured bot is installed. The second sentence explicitly rules out a broader interpretation ('This is not a global server search'), which separates it from the search-style siblings like ads_discord_member_search and ads_discord_message_search.

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 negative guidance ('not a global server search') implies this is the enumeration path rather than a query path, but the description never says positively when to pick this over ads_discord_channel_list or ads_discord_status, nor what prerequisites exist (e.g., bot must be configured).

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