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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context not in the annotations: the full state machine and the fact that completed jobs carry a 1-hour (expiring) download_url. It stops short of stating which states are terminal or what a failed job implies.

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 short sentences, front-loaded with the purpose and then the return-value detail. No filler or redundant restatement of the tool name.

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 getter with no output schema, the description carries the important return information: the status vocabulary and the presence of an expiring download URL on completion. It leaves a gap on terminal states and failure handling, but the core contract is complete.

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 0% and the single job_id parameter is undocumented in both the schema and the description. The description never says where the job_id originates (create_caption_job/start_caption_job) or whether it is a UUID or opaque string, so it does not 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 gives a specific verb and resource ("Get a job's status") and enumerates the exact status values, so the agent knows precisely what comes back. It does not differentiate from the sibling wait_for_caption_job, which also surfaces job status, so the agent must guess which one to use for polling.

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: a one-off status check keyed by job_id. There is no explicit guidance on when to poll this repeatedly instead of calling wait_for_caption_job, nor when the job_id is available (e.g., after create_caption_job or start_caption_job).

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