get_task

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

With no annotations, the description carries the full behavioral burden. It discloses that it returns the 'current status and latest result payload' but says nothing about authentication requirements (notable given a 'login' sibling), polling behavior, terminal task states, or error handling for invalid task ids.

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 states the action, the resource, and what is returned, with no filler. Every clause earns its place.

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 two-parameter read tool with 100% schema coverage and no output schema, the description is minimally sufficient, but with no annotations it should do more to explain return semantics (e.g., pending vs. completed shapes) and auth expectations. The gaps are modest rather than severe.

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 100%: task_id and action are both documented in the schema, including the enum values for action. The description adds no syntax, format, or origin detail beyond what the schema already states, so the baseline of 3 applies.

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 ('Fetch') and resource ('current status and latest result payload for a nano-banana task'), which is precise enough for an agent to know what it retrieves. It does not explicitly differentiate itself from siblings like edit_image or text_to_image, though the 'task' framing implies post-creation polling.

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?

Usage is only implied: the reference to a 'task' and the schema's async-endpoint action enum suggest this is a polling tool used after creating a task. There is no explicit guidance on when to call it, how often, or what to do instead if the task does not exist yet.

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