Get Render Status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the asset URL returned is temporary, which is useful output context, but 'Read operation' merely restates readOnlyHint and no auth/rate-limit/expiry behavior is described.

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?

Front-loaded with the core purpose in a single efficient sentence. The Base URL line is boilerplate but compact, and nothing is padded or redundant at length.

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?

There is no output schema, and the description compensates by naming the salient return fields (status, temporary asset URL, details). For a simple two-parameter read tool this is nearly complete, lacking only lifecycle context such as when the temporary URL expires.

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 100%, so the schema already documents both 'id' and 'account'. The description only echoes the 'by ID' lookup concept and adds no format, source, or account-selection detail beyond the 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?

Uses a specific verb ('Get') plus resource ('render') and enumerates what is returned: rendering status, temporary asset URL, and details. It is clearly distinguishable from the sibling 'render' (which creates) and from the template/asset tools, though it does not explicitly name 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?

The phrase 'by ID' and 'Read operation' imply this is a lookup used to poll or inspect an existing render, but there is no explicit when-to-use versus when-not, nor any named alternative such as list/filtering tools. Usage is inferred rather than stated.

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