feedback-capture

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

The description discloses useful behavior: it renders exactly one view and produces a PNG visible to the agent. However, with no annotations provided, it does not mention that rendering is non-destructive, how the PNG is returned, or performance/side effects.

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 with no filler or redundancy. It earns its place by stating the core operation and output format.

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 parameters, no annotations, no output schema, and closely related sibling tools like feedback-capture_views and render-still, one sentence is under-specified. It lacks alternative selection guidance, output return details, and parameter clarification.

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 for parameter meaning. It only partially does so for 'view' via 'named or the live scene camera', which overlaps with the schema title, and says nothing about res, object, or shading.

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 clearly states the action ('Render'), the object ('one view'), and the output ('to a PNG the agent can see'). It is specific enough to convey the tool's function, though it does not explicitly name sibling tools like feedback-capture_views.

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 about when to use this tool versus alternatives such as feedback-capture_views, render-still, or ui-screenshot. There are no exclusions or 'when-to-use' statements.

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