Subscribe to events

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

Description explains the subscription behavior (buffering, reading via get_recent_events). Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted; description adds context about side effects.

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?

Description is efficient (3 sentences) with all essential information front-loaded—purpose, usage, and alternatives—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?

Covers parameters, workflow (subscribe then get_recent_events), and event type examples. No output schema, but description provides sufficient context for use.

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%; description lists event types but does not significantly add beyond schema descriptions. Baseline 3 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?

Description uses a specific verb ('record real-time activity') and resource ('events'), and explicitly distinguishes from sibling tools like create_event and schedule_message.

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?

Clearly states when to use ('observe what is going on now') and explicitly contrasts with alternatives (create_event, schedule_message), providing clear guidance.

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