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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds minimal context by noting it returns a 'status/result,' hinting at the return content. It doesn't contradict the annotation (Get aligns with readOnlyHint). It adds little beyond the annotation but is consistent.

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?

One clean, front-loaded sentence with no wasted words. It is efficient and immediately states the purpose. However, the brevity partly reflects under-specification rather than deliberate conciseness, which keeps it from a 5.

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, the description should explain what 'status' and 'result' actually look like — e.g., possible statuses (queued, running, completed, failed) and how to interpret them for polling. It provides none of this. For a polling tool, the agent lacks the information needed to know when a job finishes or what constitutes success.

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%, so the description must compensate for the undocumented job_id parameter. It does not mention job_id at all — neither its meaning nor where to obtain it (presumably from a generation call's response). With a single required parameter and zero schema documentation, this is a clear 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: 'Get the status/result of a generation job.' It is specific about what the tool does. It doesn't explicitly differentiate from siblings, but none of the sibling tools (video_editor_*, media_forge_generate) directly offer job-status retrieval, so it is reasonably distinct by nature.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it should be called after media_forge_generate to poll for completion, nor how statuses should be interpreted (e.g., when a job is finished). No exclusions or alternative references are given.

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