blender_render_tiled

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by listing default views ('iso/front/right/top'), available angles, and the effect of focus_object/isolate. It does not describe output format or potential side effects, but with strong annotations this is sufficient.

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 compact and front-loaded: a strong lead sentence, a line on available angles, and a usage tip with a follow-up suggestion. Every sentence earns its place, with no redundant or filler content.

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?

Given four optional parameters, no output schema, and a rich sibling set, the description covers the primary use case, angle choices, zoom-related parameters, and a follow-up tool. It misses the 'zoom' parameter and does not describe the output format, but the essential context for selection and invocation is present. The lack is minor because zoom is self-explanatory and the described workflow is actionable.

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 0%, so the description must compensate. It explains the 'angles' parameter via 'Default views' and 'Available: iso, front, back, right, left, top,' and clarifies focus_object and isolate ('zoom into a specific part'). However, the 'zoom' parameter is not mentioned at all, leaving one of four parameters without any description-level semantics.

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 opens with '4-angle labeled grid render — your primary feedback tool after every modeling step,' clearly stating the tool produces a multi-angle labeled grid render and establishing its role. It differentiates from sibling tools like blender_render_turntable by emphasizing '4-angle labeled grid' and later suggesting cross_section_gallery as a follow-up, which distinguishes this tool's purpose.

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?

Explicitly prescribes when to use: 'your primary feedback tool after every modeling step.' It provides concrete usage hints for parameters ('Use focus_object (+isolate) to zoom into a specific part') and recommends an alternative for internal geometry verification ('Follow up with cross_section_gallery if internal geometry needs verification'), giving clear when-to-use and when-not-to-use guidance.

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