subscribe_events

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the subscription is persistent, how events are delivered, whether unsubscribe_events is required to stop it, rate limits, or auth requirements. 'Real-time event streaming' is the only behavioral hint.

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?

One efficient sentence with no waste, front-loaded verb+resource. Nothing extraneous, though being a single short sentence it also carries no structure to organize richer content.

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?

An output schema exists so return values need not be explained, but for a subscription tool with 0% param coverage, no annotations, and no lifecycle/cleanup context (unsubscribe_events is a sibling), the description leaves substantial gaps an agent needs to invoke it correctly.

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 both parameters (event_types, priority_threshold) lack any description in the schema. The children tool description mentions 'specified event types' generically but adds no meaning for priority_threshold or valid event type values.

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 verb (subscribe) and resource (real-time event streaming) which is clear enough. However it does not distinguish itself from siblings like poll_events or subscribe_mission_updates, leaving the agent to infer the difference between streaming subscription and polling.

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?

No when-to-use guidance, no mention of when to prefer this over poll_events or subscribe_mission_updates, and no prerequisites or cleanup (unsubscribe_events) noted. The agent gets no routing help.

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