retrieve_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. It does not say whether the call blocks until completion, what happens for an unknown or expired task_id, whether the result field is null while pending, or whether the operation is free of side effects — all material for a task-status endpoint.

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?

One front-loaded sentence with no filler, which is good structure, but the brevity reflects under-specification rather than economy — nothing about state, errors, or return shape is included.

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 output schema and no annotations, the description is the only source of truth, and it omits the lifecycle contract an agent needs: pending/in-progress/failed statuses, what 'result' contains, and whether repeated polling is expected. It gestures at the return concept but is not complete enough to call correctly in a multi-step pipeline.

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% for the single parameter task_id, and the description never mentions it. It is left implicit that the ID comes from create_retexture_task, and no format expectations (UUID vs. opaque string) are given, so the description fails to compensate for the schema gap.

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 ('Retrieve') and resource ('retexture task'), plus what is returned ('status and result'). It does not distinguish itself from siblings like list_retexture_tasks or stream_retexture_task, so an agent must infer the single-task vs. multi-task vs. streaming split from the name 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?

There is no guidance on when to use this versus stream_retexture_task (live updates) or list_retexture_tasks (enumeration), nor any mention of polling cadence or whether the call blocks. The agent must guess the intended workflow from the sibling names.

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