upscale_image

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

Without annotations, the description should disclose behavioral traits. It mentions returning task id, status, and output URLs, but does not explain what terminal status means, whether the task is asynchronous, or any limitations (e.g., image size, auth requirements). The polling mechanism is not 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?

The description is a single sentence, concise and front-loaded, but it omits necessary details about behavior and parameters, prioritizing brevity over completeness.

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 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain how to use the returned task id, the meaning of status values, or the lifecycle of the task. The parameter behavior (polling) is not contextualized.

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 only 33% (only 'wait' has a description). The description adds no parameter-specific explanations for 'timeout_ms' or 'poll_interval_ms', leaving their semantics unclear despite the low coverage.

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 clearly states it creates a Grok Imagine task for upscaling an image and returns a task id, status, and output URLs. The verb 'create' and resource 'upscale image' are specific, and the tool distinguishes from sibling tools like text_to_image or text_to_video.

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 on when to use this tool vs alternatives or how to interpret the returned task id. It does not explain the polling behavior implied by the parameters (wait, timeout_ms, poll_interval_ms) or when to set them.

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