get_task

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

The description reveals it returns status and payload, but with no annotations, it lacks detail on idempotency, error handling, or rate limits. The mention of 'current' implies it may change, but not elaborated.

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?

Single sentence, front-loaded with verb and resource, no extraneous words. Efficient and clear.

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?

Adequate for a simple fetch tool with two parameters (100% schema coverage). Lacks output schema, but description covers what is returned. Could mention that it does not mutate state.

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 description adds context by specifying 'imagen-4 task', which is beyond the schema's parameter descriptions. Schema coverage is 100% but the description enriches understanding with task type.

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 'Fetch the current status and latest result payload for a imagen-4 task,' specifying the verb and resource. It distinguishes from siblings like 'remix_image' and 'text_to_image' which create tasks, while this fetches status.

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 explicit guidance on when to use or alternatives. It is implied that this tool is used after creating a task to check its status, but there are no exclusion criteria or mention of sibling tools.

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