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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does indicate this is a read-only lookup ('Get'), names the possible job states, and mentions progress/result metadata. It does not disclose polling semantics, failure behavior, or whether repeated calls have side effects, though the absence of such notes is less critical for a simple status endpoint.

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?

The description is a single well-structured sentence that front-loads the action and resource, then adds useful status enumeration and result metadata without any filler.

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 one-parameter status look-up, the description covers the core purpose and return highlights, but it omits important usage context: how job_id is obtained, that this is a polling operation after brode_convert, and when a job can be considered final. Sibling tool names imply this flow but do not make it explicit.

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?

The schema has one required job_id with a UUID format, and schema description coverage is 0%, so the description needs to compensate. The description does not explain where job_id comes from, what it refers to beyond 'conversion job', or any constraints. The natural meaning of 'job_id' is understandable, but the description adds essentially no parameter-level guidance.

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 uses a specific verb ('Get') and a clear resource ('status of a conversion job'), and it enumerates the possible states: queued, processing, completed, failed. It also mentions progress stage and result metadata, making it clearly distinct from the sibling conversion, download, and preset tools.

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 implies this is a polling/status-check tool, likely used after brode_convert and before the job can be downloaded. However, it does not explicitly state when to use this tool versus brode_download, nor does it say that job_id must come from a prior conversion call.

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