media.job.run_once

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

With no annotations, the description must carry behavioral disclosure. It does add the useful non-blocking trait, but it fails to disclose return values, error behavior, side effects, idempotency, or whether repeated calls are safe. This is a meaningful gap for a state-advancing operation.

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 one focused sentence that front-loads the action and scope. Every word earns its place and there is no redundant phrasing.

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 job-advancing tool with no annotations, no output schema, an underspecified input schema, and a close sibling media.job.tick, the description is too terse. It does not explain what a step produces, how a durable job progresses, or what response the agent should expect.

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 schema oddly declares jobId as required but defines no properties, so the schema itself gives almost no parameter semantics. The description does not mention jobId, its format, or how to identify the job, so the agent is left to infer from the tool name and the word 'job'.

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 states a specific verb ('Advance') and resource ('one durable job') with explicit scope ('by one non-blocking step'). It is clear about what the tool does, but it does not differentiate itself from the similar sibling media.job.tick, so it misses the highest level of clarity.

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 guidance about when to use run_once versus alternatives such as media.job.tick or media.job.status. The only hint is the action itself, which gives implied use rather than explicit selection criteria or exclusions.

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