blender_render_report

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a list of reported fields but no further behavioral detail (e.g., whether a scene must be loaded, error conditions, or performance implications). It does not contradict the annotations and adds minimal extra context beyond the field list.

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 sentence that front-loads the action ('Report') and lists the key data points compactly. It is not bloated, though the comma-separated list makes it slightly dense. Overall, it earns its place with no redundant wording.

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 report tool with one optional parameter and no output schema, the description covers the essential information an agent needs to know: what fields will be reported. It does not mention the return format explicitly, but the response_format parameter already handles that. It is sufficient for a read-only informational tool.

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 parameter response_format is fully described in the schema (enum values and descriptions), so schema coverage is 100%. The description adds no additional meaning to the parameter, staying at the baseline for high coverage.

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 uses a clear verb 'Report' and specifies the resource (render configuration) and the exact data points (engine, resolution, frame range, etc.). It is unambiguous and distinguishes itself from sibling tools like blender_render (which actually renders) and blender_settings_report (which likely reports general settings) by focusing on what a render would actually use.

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 description implies usage before rendering or to audit render settings, but it does not explicitly state when to use this tool over alternatives like blender_settings_report or blender_render. No exclusions or alternate conditions are provided, so an agent must infer from the purpose alone.

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