render_history

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

With no annotations provided, the description carries the full behavioral burden, but it only states durability and ordering. It does not disclose whether in-progress or failed renders are included, what fields each entry contains, or anything about permissions or response shape.

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?

One short sentence with no filler; the resource, ordering, and durability trait are all front-loaded. 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 tool with one optional parameter, this is nearly adequate: an agent can invoke it safely with no args or with a limit. However, with no output schema, the description does not explain what a history entry contains or how to correlate entries with other render tools.

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 single `limit` parameter is fully constrained in the schema with type, default, minimum, and maximum. The phrase 'most recent first' gives it contextual meaning as limiting the number of recent history entries returned, even though the description does not mention the parameter directly.

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?

Identifies the resource ('render history') and a key ordering trait ('most recent first'), making it distinguishable from render_status or render_get_output. It lacks an explicit verb like 'list' or 'get', but the intent is clear from the name and wording.

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?

No guidance is given on when to use this tool versus render_status, render_get_output, or other render-related siblings. The word 'history' implies a past-facing view, but the description never states this explicitly or names alternatives.

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