stream_remesh_task

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

With no annotations and no output schema, the description carries the full disclosure burden, yet only 'Stream updates' is offered. It does not say what an update contains (status, progress, result), whether the stream terminates on completion, or whether the call blocks, which are critical for a streaming tool.

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 waste, but it is under-specified rather than concise. The brevity costs more than it saves given the missing behavioral and parameter context.

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 streaming tool with no annotations, no output schema, and zero parameter documentation, the description leaves out everything an agent needs beyond the bare action: stream lifecycle, update payload shape, and timeout semantics.

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 0%, so the description must compensate and it does not. task_id is self-evident from its name, but timeout is completely unexplained — no units, no default, no statement of what happens when it elapses.

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 specific verb and resource: 'Stream updates for a remesh task.' An agent can tell it is the streaming variant of the remesh family, but the description never contrasts it with retrieve_remesh_task or list_remesh_tasks, so sibling differentiation is left to the naming convention.

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?

There is no guidance on when to stream rather than poll with retrieve_remesh_task or list_remesh_tasks, nor any precondition such as the task needing to already exist. The agent must infer the choice entirely from the tool name.

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