stream_retexture_task

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the verb: no indication of transport, whether the call blocks, whether it terminates at task completion, what the timeout parameter governs, or what happens on an unknown/expired task_id. One partial credit for at least establishing that output is incremental updates.

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 filler, so it is not bloated. But the economy comes at the cost of substance rather than from efficiency — nothing unnecessary, yet not enough necessary content.

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 endpoint with no annotations, no output schema, and zero parameter documentation, the description should cover at minimum termination semantics and what a consumer receives. None of that is present, so an agent cannot confidently invoke or interpret the call from this definition alone.

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% — neither task_id nor timeout is documented in the schema, and the description mentions neither. "For a retexture task" loosely implies task_id's meaning, but the timeout parameter (units, default, whether it bounds the whole stream or each poll) is completely unspecified in both description and schema.

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 ("stream") and resource ("retexture task"), which is more than a tautology. However it never distinguishes streaming from the sibling retrieve_retexture_task, nor explains what a "stream" returns (SSE, long-poll, incremental diffs), so an agent must infer the retrieval-vs-stream split from naming alone.

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 statement of when to use this instead of retrieve_retexture_task or list_retexture_tasks, and no guidance on whether streaming is appropriate for one-shot status checks. The only hint is the word "stream" in the name/description.

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