madeonsol_stream_session_kill

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

Provides detailed behavioral info: returns specific status codes (200, 404, 400) with response shapes. Notes that it frees a connection slot. Annotations already indicate destructive and idempotent, but description adds concrete return scenarios.

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?

Single sentence plus return details. Every word 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?

Complete for a simple tool: effect, returns, error cases, and annotations cover safety. No output schema needed.

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 covers 100% with description for id. The tool description adds context that id comes from stream_sessions_list and clarifies the positive integer constraint, reinforcing schema. Returns for invalid inputs (400/404) provide extra clarity.

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?

Clearly states the verb 'evict' (force-disconnect) and the resource 'live WebSocket streaming session by id'. The action of freeing a connection slot distinguishes it from sibling tools like stream_sessions_list.

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?

Implicitly indicates usage when you have a session id to disconnect. Mentions 'PRO/ULTRA only' as a restriction. No explicit when-not-to-use or alternatives, but the action is distinct from siblings.

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