sse_generate_client

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 discloses only one behavioral trait ('reconnection') but omits critical details: what files are generated, whether existing files in 'directory' are modified, what language/framework the client targets, and how api_key is involved.

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?

The phrase is front-loaded and wastes no words, with the core action stated immediately. However, it is so terse that it borders on under-specification rather than genuine conciseness for a tool that likely generates multi-file code.

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 annotations, no output schema, a 50% schema coverage gap, and a single-line description, an agent cannot predict what the tool will produce, where it writes, or why api_key is required. For a client-generation tool with two parameters, this is materially incomplete.

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 50% — only 'directory' has documentation. The tool description adds no meaning for either parameter: 'api_key' remains completely unexplained, and nothing in the description connects 'directory' or 'api_key' to the generation process.

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 states a specific verb ('Generate'), a specific resource ('SSE client'), and a distinguishing feature ('with reconnection'). It implicitly differentiates from sibling sse_generate_server (client vs. server), though it does not explicitly contrast with ws_generate_client or http_generate_wrapper.

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 is given on when to use this tool versus alternatives. With siblings like sse_generate_server, ws_generate_client, and ws_add_rooms, the agent receives no help choosing between SSE and WebSocket transports or deciding when the reconnection feature is needed.

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