List recent creative jobs

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral detail that results are ordered newest-first and are workspace-scoped, but says nothing about pagination behavior despite the presence of limit/offset.

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?

Two tight sentences with no filler; the core action and ordering come first, filters second. Every sentence earns its place.

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?

For a read-only list tool with no output schema, the description should clarify paging (limit/offset) and roughly what a job record contains. It covers scope, ordering and filters but leaves pagination and result shape unaddressed.

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 only 25% (only 'limit' is documented), so the description must compensate; it partially does by naming status and asset_type as filters. However offset is left entirely without meaning and the enum values for status/asset_type are never explained in the description.

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 a specific verb and resource ('List recent image and video jobs') plus scope ('in the workspace') and ordering ('newest first'). It is clear what the tool returns, though it does not explicitly distinguish itself from single-job siblings like adsoptimiser_get_job or adsoptimiser_list_pipelines.

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 second sentence implies usage by naming the two filterable dimensions, but there is no explicit when-to-use guidance nor any reference to the alternative tools (get_job for one job, list_pipelines for pipelines). Usage is inferable but not stated.

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