bvoiz_get_job_status

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

No annotations are provided, so the description carries the full burden, yet it says nothing about read-only semantics, whether the call blocks, how long polling lasts, or what happens if the job fails or the ID is unknown. The polling-until-complete behavior is disclosed only in the schema's wait_until_complete property, not in the description.

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?

A single front-loaded sentence with no filler for a simple retrieval tool. It is appropriately sized, though it is arguably too thin rather than too wordy.

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 read-only status-check tool with full schema coverage and no annotations, the description covers the essential purpose but omits the meaningful behavioral facts an agent needs: default non-blocking return, the polling semantics of wait_until_complete, and behavior on error or non-existent IDs.

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 100%, so all three parameters (job_id, api_key, wait_until_complete) are already documented. The description's only added nuance is that job_id may be a Job ID or Request ID, which the schema also states, so it does not go beyond structured data.

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?

States a specific verb and resource ('Kiểm tra trạng thái tiến trình tạo âm thanh nền' – check status of background audio generation) and names the lookup key (Job ID or Request ID). This distinguishes it from siblings like bvoiz_synthesize_speech or bvoiz_download_audio, though it never explicitly says it is the polling counterpart to a submitted synthesis job.

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?

Usage is only implied: the mention of Job ID/Request ID suggests it is called after submitting a job, but no when-to-use/when-not-to-use guidance is given. The description does not mention the alternative behavior of blocking vs. non-blocking retrieval, which is the main branching decision an agent faces.

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