feedback-lookdev

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

Annotations are absent, so the description carries the full burden of behavior disclosure. It only states what the tool does ('render') and what it returns ('quality analytics'), but does not disclose whether it modifies the scene, how long the render might take, whether it requires a specific context (e.g., an active object), or what 'quality analytics' includes. This is minimal and leaves significant unknowns.

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, concise sentence that front-loads the primary action and outcome. There is no fluff, repetition, or unnecessary detail. It adheres to minimalism while staying on topic.

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?

The tool is moderately complex (rendering a turntable, returning analytics) with three parameters, no output schema, and no annotations. The description does not explain what 'quality analytics' entails, what the output looks like, how parameters affect the process, or any setup requirements. It lacks essential context for an agent to use it effectively.

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%, meaning the description must explain the parameters (res, count, object) to compensate. The description mentions none of them. It only talks about 'material-shaded lookdev turntable' and 'quality analytics', giving no clue about resolution, frame count, or object selection. This is a critical failure for parameter understanding.

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 verb and resource: 'Render a material-shaded lookdev turntable and return quality analytics.' It specifies the action (render) and the subject (lookdev turntable) and mentions the additional deliverable (quality analytics). It distinguishes from similar siblings like feedback-turntable or feedback-quality by adding 'material-shaded' and 'lookdev', though it does not explicitly differentiate itself.

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 provided on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or when not to use it. The sibling list includes several feedback-* tools (e.g., feedback-turntable, feedback-quality), but the description gives no context on how this one differs or when it is preferred. This leaves the agent without decision support.

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