createMediaSmartCoverJob

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'create' which implies a write/mutation operation, but it doesn't disclose any behavioral traits like permissions needed, side effects, rate limits, or what the job does (e.g., processing media for covers). This leaves significant gaps in understanding the tool's behavior.

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, concise sentence ('创建媒体智能封面任务') that is front-loaded and wastes no words. However, it's overly brief to the point of under-specification, which slightly reduces its effectiveness despite the efficient structure.

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 the complexity of a job creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the job does, what it returns, or any behavioral aspects, making it inadequate for an agent to understand the full context of invoking this 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 description adds no meaning beyond what the input schema provides. The schema has 100% description coverage, with 'objectKey' documented as '对象在存储桶里的路径' (path of the object in the storage bucket). Since the schema fully describes the single parameter, the baseline score of 3 is appropriate, as the description doesn't compensate or add extra context.

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 '创建媒体智能封面任务' (Create media smart cover job) states a clear verb ('create') and resource ('media smart cover job'), but it's vague about what this actually does. It doesn't specify what a 'media smart cover job' entails or what resource it creates, nor does it differentiate from sibling tools like 'createDocToPdfJob' or 'describeMediaJob' beyond the basic resource name.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as when to choose this over other job-related tools like 'createDocToPdfJob' or 'describeMediaJob'. There's only a basic statement of purpose without usage context.

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