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

Annotations already establish the safe read-only, idempotent, non-destructive profile, so the bar is lower; the description adds real value by disclosing the project lifecycle states (queued|processing|preview_ready|ready|expired|failed), the expiresAt/expiringSoon signals, and the important caveat that a finished job whose project is expired has no downloadable video. It does not describe rate limits or auth requirements.

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 dense but front-loaded sentence that leads with the primary output (job status) before secondary details. Slightly overloaded with parenthetical enumerations, but no wasted framing.

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 does carry the return-value burden well, listing the fields and expiry caveat, so an agent knows what it gets back. However, it is silent on the two input parameters, leaving a gap for a tool that requires projectId.

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 there are two parameters, yet the description only gestures at the project via prose and never explains projectId's format/role or what brandId is for. It does not compensate for the completely undocumented schema.

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: retrieving the latest render job of a video editor project, and enumerates what comes back (status, stage, progress, error code, project state, URL). It is clearly distinguishable from list_video_projects or get_video, though it never names an alternative to contrast against.

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 explicit guidance on when to call this versus siblings like list_video_projects or get_video, and no stated prerequisites. Usage is only implied by the phrase 'Get the latest render job'.

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