get_task

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

No annotations are provided, so the description carries the full burden. 'Fetch' clearly indicates a read-only operation, and the description states what data is retrieved (status and result payload). It does not mention potential errors or polling behavior, but for a simple fetch tool this is adequate.

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, concise sentence that immediately communicates the tool's function without any redundant or extraneous information.

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 simple fetch operation with fully documented parameters, the description sufficiently covers the tool's purpose and output (status and payload). The absence of an output schema is mitigated by the explicit mention of what is returned.

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?

The schema fully documents both parameters with descriptions (task_id, action) and an enum for action. The tool description adds no additional parameter-specific meaning beyond indicating the task context, so the baseline of 3 applies due to high schema 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 uses the specific verb 'Fetch' and identifies the resource as 'current status and latest result payload for an imagen-4 task,' which precisely matches the tool name and distinguishes it from sibling generation tools like remix_image and text_to_image.

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 description clearly implies this tool is used to retrieve the status/result of a previously created imagen-4 task, and the parameters (task_id, action) reinforce that. It does not explicitly state 'use this after calling text_to_image or remix_image,' but the context is clear from the tool name and sibling tools.

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