describeMediaJob

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 describes a query operation ('查询'), implying it's likely read-only, but doesn't confirm this or mention other traits like rate limits, authentication needs, or error handling. For a tool with zero annotation coverage, this is insufficient to fully inform the agent about behavioral expectations.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an AI agent to parse quickly. Every part of the sentence contributes to understanding the tool's function.

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 tool's low complexity (1 parameter, no output schema, no annotations), the description is adequate but has gaps. It explains the basic purpose and parameter source, but lacks details on behavioral traits, usage context, and output format. Without annotations or an output schema, the description should do more to compensate, but it meets a minimum viable standard.

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 minimal semantic context: it implies the tool uses a jobId to query results, but the input schema already provides 100% coverage with a clear description for the jobId parameter. Since schema_description_coverage is high, the baseline is 3, and the description doesn't significantly enhance understanding beyond what the schema states.

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 clearly states the tool's purpose: '根据 jobid 查询指定的媒体智能封面任务结果' (Query specified media smart cover job results based on jobid). It specifies the verb (query/describe) and resource (media smart cover job results), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'createMediaSmartCoverJob' or 'describeDocProcessJob', which prevents a perfect score.

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 minimal usage guidance: it mentions that jobId can be obtained from the response of submitting a smart cover task. However, it doesn't specify when to use this tool versus alternatives (e.g., when to query results vs. create a job), nor does it provide context on prerequisites or exclusions. This lack of explicit guidance limits its helpfulness for an AI agent.

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