event_list_subscribers

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

With no annotations, the description carries the full burden. It implies a read-only operation via 'list' but does not explicitly state it is non-destructive or mention any side effects. The minimal disclosure is adequate but not enriched.

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 extremely concise: one line for purpose plus a parameter section. There is no filler, and the key information is front-loaded. Every sentence earns its place.

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 list tool, the description provides enough context: it explains filtering parameters and what the tool does. The output schema exists to document return values. A minor gap is no definition of 'active', but overall it is complete.

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 provides no parameter descriptions (0% coverage), so the description adds essential meaning: examples for 'event' (e.g., E_DLG_LOAD) and 'socket' (e.g., udp:1.2.3.4:8080). This clarifies format and usage beyond the schema.

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 active event subscribers with optional filtering. The verb 'list' and resource 'event subscribers' are specific, and it distinguishes from sibling tools like 'event_list' (lists events) and 'event_subscribe' (subscribes to events).

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 provides no guidance on when to use this tool versus alternatives. Although it mentions optional filtering, it does not explain when to choose this over related tools like 'event_subscribe' or 'event_list', lacking exclusion criteria.

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