discord_get_event_subscribers

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds valuable behavioral context: page size up to 100 users, cursor-based pagination with nextCursor and after parameter usage. It also reveals the return shape. This adds information beyond annotations without contradiction.

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 two short sentences. The first sentence states the purpose directly. The second sentence explains pagination and read-only nature. Every word earns its place; no redundancy or fluff. Ideal for quick parsing by an AI agent.

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 the tool involves pagination, the description covers the core behavior (page size, cursor usage). There is an output schema, so return values are documented. No further information about permissions or rate limits is necessary for this read-only tool. The description is sufficient for correct invocation.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining pagination: 'pass nextCursor back as after to fetch next page' and 'page holds up to 100 users'. This relates the 'after' and 'limit' parameters to the behavior, enhancing understanding beyond the schema definitions.

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 lists users marked as 'Interested' in a scheduled event. The verb 'List' and resource 'scheduled event subscribers' are specific. This tool is distinct from siblings like 'discord_get_scheduled_event' or 'discord_get_reactions', so purpose is unambiguous.

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 explains pagination behavior (when to use 'after' cursor) and notes the tool is read-only. It implicitly tells when to use this tool: to get interested users for a scheduled event. However, it does not explicitly state when not to use it or compare with alternatives, so it's clear but slightly lacking exclusion guidance.

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