Get a render

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that the tool returns status, download URL, and error, which is useful, but it does not disclose behaviors like not-found handling, URL expiration, or auth requirements. With annotations present, the bar is lower, and this meets it without contradiction.

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 concise sentence that front-loads the key output fields and includes the id format. Every word contributes value with no redundancy.

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 single-parameter read tool with no output schema, the description adequately covers what the tool returns and what the id should look like. It could add more about error/not-found behavior, but the core information an agent needs to call it correctly is present.

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 schema only says id is a string. The description compensates by specifying the expected id format (rnd_…) and clarifying that it is a render id, which is meaningful beyond the raw 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?

The description identifies the resource (a render), the key identifier format (rnd_…), and the returned information (status, download URL, error). While it is a noun phrase rather than an explicit verb phrase, the title 'Get a render' supplies the verb, and the content clearly separates this read tool from siblings like render (creation) and list_templates.

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 implied: call this when you have a render id and need its status or download URL. There is no explicit when-not-to-use guidance or mention of alternatives, though the sibling list makes it inferable that render creates and convert_to_pdf converts.

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