get_task

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does ('Fetch current status and latest result payload') but does not clarify side effects, error behavior, rate limits, or authentication requirements. The verb 'fetch' implies a read operation, but this is not explicitly stated and adds little behavioral context beyond the purpose.

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 of 10 words, concise and front-loaded with the action ('Fetch current status and latest result payload'). Every word contributes to clarity with no redundancy.

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 tool is simple and the schema covers parameters well, but the description omits important context such as authentication prerequisites (given a login sibling tool) and potential error scenarios. There is no output schema, so the description's mention of 'latest result payload' provides some return information, but overall completeness is adequate with clear gaps.

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%, with both parameters (task_id, action) clearly described in the input schema. The tool description does not add additional parameter meaning, but the schema suffices, so baseline 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 resource ('current status and latest result payload for a topaz task'), clearly distinguishing it from sibling tools like upscale_image/upscale_video (which likely create tasks) and check_pricing. It unambiguously communicates the tool's function.

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 implies usage (fetching task status after creation) but does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites like authentication. It provides no when-not-to-use guidance, so usage is only implied by the tool's purpose.

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