get-render

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

Annotations are absent, so the description carries the full burden. It discloses that job IDs are valid for the server lifetime and logs survive restarts, which is useful operational context. However, it does not state whether the operation is read-only, whether it has side effects, or what the response contains. The disclosed behavior is minimal but not misleading.

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 two sentences with zero redundancy. The primary purpose is front-loaded, and the additional caveat about job ID validity is placed second, preserving clarity. Every word earns its place.

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 simple one-parameter status tool, the description covers the core purpose and a relevant operational detail. However, it omits what the response looks like (since no output schema exists), which an agent might need to interpret results. It is minimally complete but not fully self-sufficient.

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?

With 0% schema description coverage, the description must compensate for the single 'id' parameter. It implies that 'id' refers to a job ID by stating 'Job IDs are valid...', which gives some meaning. However, it does not explain the format, source, or how to obtain the ID, leaving the agent with partial understanding. The compensation is adequate but not thorough.

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 clearly states the action (get) and the resource (aerender job status), which is specific enough to distinguish from generic tools like get-request or bridge-status. However, it does not explicitly differentiate from sibling tools, so it lacks the extra clarity of naming an alternative.

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 guidance on when to use this tool versus alternatives. The description mentions job ID validity and log persistence, but provides no context about selection criteria or exclusions. The agent is left to infer when this tool is appropriate.

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