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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no polling/async semantics, no explanation of what the status response contains or whether the workspace must exist. It fails to earn value beyond the structured fields.

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?

It is a single short sentence, front-loaded with the core action, so nothing is wasted. But the extreme brevity functions as under-specification rather than efficient conciseness for a tool with an undocumented parameter and a near-identical sibling.

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?

With no output schema to explain return values and no parameter documentation, the description should carry more of the load. It omits what 'status' means, what the returned states are, how it relates to batch_get_work_status, and the role of workspace_id, leaving real gaps for an agent.

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 description coverage is 0% and the single workspace_id parameter has no format, required-ness, or example detail. The description's single short clause mirrors the schema-level note and adds no syntax or constraint information to compensate for the coverage gap.

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 clear verb+resource combination ('查询异步任务状态' / query async task status), so an agent knows the tool reads task status. However, it does not differentiate from the extremely close sibling batch_get_work_status, nor clarify that the query is scoped by workspace rather than a single task, so it falls short of a 5.

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 when-to-use guidance, no mention of when to prefer this over batch_get_work_status or get_persona_status, and no stated prerequisites. The agent must infer usage purely from the name.

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