get_task

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

The description states 'Fetch' which implies a read operation, but it does not explicitly state that the tool is read-only, idempotent, or has no side effects. Since annotations are absent, the description carries the burden for behavioral disclosure. It is minimally adequate but lacks clarity on potential errors or response structure.

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, clear sentence that immediately conveys the tool's purpose. It contains no unnecessary words and is well-structured for quick comprehension.

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?

The description covers the core purpose and mentions the output (status and payload), which is adequate for a simple retrieval tool without an output schema. However, it lacks information about error handling, pagination (unlikely), or potential delays. Given the tool's simplicity, it is mostly complete.

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 input schema already provides thorough descriptions for both parameters, including the enum constraint for action. The description does not add any new information about the parameters beyond what the schema provides. With 100% schema coverage, a baseline score of 3 is appropriate.

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 a specific verb 'Fetch' and identifies the resource: current status and latest result payload for a gpt-4o-image task. It clearly distinguishes from sibling tools like check_pricing (pricing) and text_to_image (creation), making it easy for an agent to select this tool for retrieving task details.

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 provides no explicit guidance on when to use this tool versus alternatives. It is implied that this tool retrieves tasks created by text_to_image, but no when-not or when-to-use context is provided. This could confuse agents in complex decision-making.

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