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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description goes beyond that by disclosing the concrete return content (status, seconds, and a group_id once the drawing is placed), which is the key behavioral fact an agent needs when no output schema exists.

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 compact sentence with the subject front-loaded and the returned fields trailing. Dense but not padded; only mild awkwardness in 'group_id once placed' costing a bit of readability.

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?

Because there is no output schema, the description's field list is doing useful work. However, it does not explain status values, whether results are scoped to the current project, or when an agent should re-poll versus proceed, leaving real gaps for a progress-tracking tool.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies a parameterless listing rather than accepting job IDs, which matches the empty input schema.

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 the specific resource (progress of drawings by SVG Lab's vector model) and enumerates the returned fields (status, seconds, group_id once placed). It is clear what the tool reports, though it never mentions that these jobs originate from generate_illustration/plan_illustrations, so the connection to siblings is left implicit.

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?

There is no explicit guidance on when to call this: no mention of polling after starting an illustration job, no frequency advice, no statement of what happens when no jobs exist. Usage must be inferred from the name and from the neighboring generate_illustration tool.

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