maya_viewport_capture

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

With no annotations, the description carries the full burden. It discloses the non-destructive nature (viewport grab, no Arnold render), instant execution, and return of an image. This provides adequate behavioral context for safe usage.

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 two sentences, front-loading the primary action and output. Every sentence adds value: first states what it does, second clarifies scope and use case. No fluff.

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 simple capture tool with no output schema, the description covers purpose, speed, and usage scenarios. It could mention more about output characteristics or limitations, but overall it is sufficient given low complexity.

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 description offers no parameter-specific guidance. While the input schema includes descriptions, the context indicates 0% schema description coverage, so the description should compensate. It does not mention any parameter constraints or usage tips.

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 'capture' and the resource 'Maya viewport' with output format 'PNG/JPG image'. It distinguishes from sibling tools like Arnold render by noting it is an instant viewport grab, differentiating it from other Maya tools.

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 provides clear usage context: 'verifying scene state, checking lighting, framing, and detecting issues'. It explicitly states what the tool does not do ('Does not do Arnold render') and gives a speed hint ('<1s'), guiding when to use it over alternatives.

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