incidents_stream_info

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

No annotations provided, so the description carries full burden. It details the output contents (endpoint URL, schema, reconnect policy, stats), which informs the agent of what to expect. It doesn't mention side effects or auth, but for a read-only metadata tool, this is sufficient.

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?

Two sentences: one specifying the metadata nature, one providing usage context. Every sentence earns its place. No redundancy.

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?

With no output schema, the description fully describes the return values. It's complete for a simple metadata retrieval tool, covering all needed aspects for an agent to use 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?

Tool has zero parameters, so the description adds value by explaining what the return contains. Baseline 4, and the description effectively provides context 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 provides metadata for the live SSE incident stream, specifying what metadata (endpoint URL, payload schema, reconnect policy, event-rate stats) and the context of use (before subscribing). It distinguishes itself well from sibling tools, none of which serve this metadata purpose.

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 explicitly says 'Call before subscribing to the SSE feed,' giving a clear use case. It doesn't explicitly exclude alternatives, but the context of sibling tools makes it clear this is the only tool for stream metadata. Good guidance.

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