feedback-capture_views

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

No annotations exist, so the description carries the full burden of behavioral disclosure, and it reveals almost nothing: no mention of whether rendered images are saved to files, sent to a feedback report, displayed in the viewport, or whether the operation blocks or requires render engine setup. The term 'anti-blob' adds jargon without explanation, further reducing transparency for an agent deciding whether invocation is safe and contextually appropriate.

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, front-loaded sentence of ten words — no wasted prose. However, the parenthetical '(the anti-blob)' is cryptic jargon that does not earn its place without explanation, so it loses a point despite the overall economy.

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 tool with 4 parameters, zero annotations, no output schema, and 12+ feedback-* siblings, the one-line description is insufficient: it does not clarify what 'several images' are used for, how this differs from feedback-turntable or feedback-capture, or what happens after rendering. An agent would have to infer the entire usage model from the tool name and the schema's enum titles.

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%, yet the description contributes zero parameter meaning: it does not mention res, object, preset, or shading. The schema's own titles do useful work (e.g., preset's title decodes ortho4/ortho6/orbit4; shading's title maps enum values to Workbench/EEVEE), but the rubric requires the description to compensate for low coverage and it fails to do so.

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 names a specific verb and resource: 'Render a multi-angle preset... as several images.' The parenthetical '(the anti-blob)' provides a niche signal that hints at this tool's differentiating role among the many feedback-* siblings, though the term is unexplained. It is clear enough to identify the action, but the differentiation from feedback-capture, feedback-turntable, and feedback-silhouette is only implicit.

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?

There is no statement of when to use this tool versus alternatives. It does not say 'use this when you need multiple orthogonal views' or name competing tools like feedback-capture, feedback-turntable, or feedback-silhouette. The only contextual clue is the cryptic '(the anti-blob)' which does not constitute actionable guidance.

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