start_stream

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

No annotations exist, so the description is the sole source. It fails to disclose behavioral details such as idempotency, effects of re-running, or whether the stream must be already created. 'Start' implies activation but no consequences are described.

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?

While extremely short (4 words), this is under-specification rather than conciseness. The description omits necessary detail and is not front-loaded with the most critical information.

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 the sibling tools (e.g., create_stream, stop_stream, update_stream) and the absence of annotation or output schema context, the description is wholly inadequate for an agent to understand the tool's role and effects.

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% (no parameter descriptions in schema), and the tool description does not explain the 'stream_name' parameter, its format, or its relationship to existing streams. This is a critical gap for a single required parameter.

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 'Start a SQL stream' states a verb and resource, but it is only a slightly expanded version of the tool name and does not differentiate from sibling tools like 'create_stream' or 'stop_stream'.

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 provided on when to use this tool versus alternatives (e.g., create_stream) or any prerequisites like the stream existing. The description is a single short sentence with no context.

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