start_streaming

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

No annotations provided, so description carries full burden. It does not disclose behavior: how events are delivered, long-running connection implications, error handling, or how subscriptionId affects the stream. Lacks details on what 'start streaming' entails beyond the name.

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?

Very concise, two sentences. No redundancy. However, it sacrifices necessary detail for brevity; still front-loaded with the core action.

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 complexity of real-time streaming and no annotations or output schema, the description is incomplete. Does not explain how to manage streaming, what the response is, or how to stop (despite sibling stop_streaming). Missing critical context for an agent to use 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 coverage is 0%; description adds minimal value. 'Optionally filter by specific collections' hints at the collections parameter but does not explain its format or values. The required subscriptionId is not mentioned at all. No parameter details.

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 uses a specific verb and resource: 'Start real-time streaming of AT Protocol events from the firehose'. It clearly distinguishes from sibling tools like stop_streaming and get_recent_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?

No guidance on when to use streaming versus polling or other monitoring tools (e.g., get_recent_events, monitor_keywords). Lacks when-to-use or when-not-to-use advice.

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