List event subscriptions

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

The description adds beyond the readOnlyHint annotation by specifying that buffer sizes are included. However, it does not elaborate on other behavioral aspects like the scope (e.g., bot-level subscriptions) or what constitutes 'active.' The annotation already covers the read-only nature, so the description provides moderate additional context.

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 very concise, consisting of a single phrase. It is front-loaded with the key information, though slightly lacking in structure (e.g., no sentence). Still, it is efficient with no wasted words.

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 simplicity of the tool (no parameters, read-only annotation), the description is reasonably complete. However, it does not explain what 'buffer sizes' means or provide any details about the output format. Without an output schema, this missing context reduces completeness.

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?

There are no parameters, so the schema coverage is effectively 100%. The description does not need to add parameter semantics, and the baseline score of 4 for zero parameters is appropriate.

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 subscriptions and their buffer sizes. It effectively conveys the verb (list) and the resource (event subscriptions). While it does not explicitly differentiate from siblings like subscribe_events, the distinct purpose is understandable given the verb and resource.

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 such as subscribe_events or unsubscribe_events. There is no mention of prerequisites or context where this tool is appropriate.

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