查询任务状态与结果

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

The description discloses polling behavior (every 5s) when wait_seconds>0, and notes that results contain temporary URLs valid for 24 hours. This adds useful behavioral context beyond a simple 'query' statement.

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 concise sentences with essential information front-loaded. No unnecessary words, every sentence adds value.

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 full schema coverage and no output schema, the description adequately explains return format (URLs for media) and validity period. Missing error handling details but sufficient for a status check 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?

Schema coverage is 100%, so baseline is 3. The description adds overall behavioral context but does not provide additional parameter-specific semantics beyond what the schema already describes.

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 '查询异步任务' (query async task), indicating the tool retrieves status and results. It is specific but does not differentiate from sibling 'wait_for_task', which may serve a similar purpose.

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 explains behavior when wait_seconds>0 but provides no explicit guidance on when to use this tool versus alternatives like 'wait_for_task' or when not to use it.

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