agentic_assist_stream

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

No annotations are provided, so the description carries the full burden. 'Streaming' is the only behavioral signal; nothing says whether the call mutates the flow, how the streamed output arrives, how session_id resumes a session, or what retry/iteration limits imply about side effects.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity reflects under-specification for a 10-parameter streaming tool rather than pure conciseness.

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?

For a complex 10-parameter, no-annotation, no-output-schema tool, the description is far too thin. It omits how streaming results are consumed, session semantics, mutation effects, and how it differs from agentic_assist/agentic_execute.

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 100%, so all 10 parameters are documented in the schema and the baseline is 3. The description adds no meaning beyond the schema for any parameter (provider, session_id, iterations_limit, etc.).

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?

States a clear verb (Request) and resource (streaming agentic assistance) scoped to building/editing a flow component. However, it does not distinguish itself from the closely related siblings agentic_assist, agentic_assist_run, or agentic_execute, so an agent must guess which agentic tool to pick.

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 phrase 'for building or editing a flow component' hints at context but gives no when-to-use criteria, prerequisites, or named alternatives. With four sibling agentic_* tools in the list, the absence of routing guidance is a real gap.

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