Get Modellix Image Task

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: it normalizes the status and hides temporary result URLs, which goes beyond the basic safety profile. It does not detail error handling, but that is not required given the strong annotations and output schema.

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, front-loaded sentence that efficiently communicates the tool's purpose and key behavioral trait. Every word adds value, with no wasted content.

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?

Given that an output schema exists, the description needn't explain return values. It covers the core functionality and adds the important privacy behavior. However, it does not place the tool within the broader Modellix workflow (e.g., how it relates to prepare/submit/finalize steps), though this is a minor gap for a simple read-only query.

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?

With 0% schema description coverage, the description carries the burden for parameter meaning. It implies that taskId identifies a task recorded in the workspace, but adds minimal detail about the parameter's format or source. Since there is only one parameter and the schema includes a pattern, this is adequate but not rich.

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 the verb 'Query', the resource 'one task recorded in this workspace', and the specific behavior 'return normalized status without exposing temporary result URLs'. This distinguishes it from sibling tools like list_modellix_canvas_tasks and get_modellix_canvas_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?

The description provides clear context: it is for querying a single task's normalized status, and the phrase 'without exposing temporary result URLs' implies a use case where URL privacy matters. However, it does not explicitly name alternatives or state when not to use it.

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