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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description adds useful context beyond the annotation by stating the verified-member auth requirement and naming returned data: jobs, your tier, hourly claim limit, and credits. It does not mention pagination, ordering, or rate limits, but it meaningfully enriches the behavioral picture.

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 compact sentence fragment that front-loads the access condition and then lists the relevant job and account information. It is appropriately sized for a simple list tool, though the noun-phrase structure is slightly terse rather than fully sentence-like.

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 one-parameter, read-only list tool with full schema coverage and no output schema, the description supplies the key missing context: verified-member access and the categories of data returned. It leaves pagination and ordering unspecified, but the core information needed to select and invoke the tool is present.

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 coverage is 100%, so the token parameter is already documented as a membership token. The description's 'Verified members only' adds a mild access condition, but it does not provide format, validation, or source details for the token beyond what the schema already supplies.

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 identifies the resource as open AboveEveryName image/clip generation jobs and adds member-specific data such as tier, hourly claim limit, and credits. This distinguishes the tool from generic task-list siblings, but it does not explicitly state the verb 'list' or directly contrast with studio_claim_job and list_tasks.

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 phrase 'Verified members only' gives a clear access prerequisite, and 'open ... jobs' implies the browsing use case. However, it does not say when to use this tool instead of alternatives like studio_claim_job or list_tasks, nor does it specify any exclusions.

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