keyshot_inspect_scene

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

With no annotations, the description must fully disclose behavior. It states the tool 'opens' a scene (implying a read operation) and returns data, but does not clarify if it modifies state, what happens on invalid paths, or whether scene locking occurs. Key behavioral aspects are omitted.

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 conveys the core functionality without extraneous words. It is well-suited for a simple tool, though a brief example or structured list could improve scanability without harming conciseness.

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 the lack of output schema, the description should elaborate on what 'objects, cameras, materials, and scene metadata' includes. It also doesn't mention return format or error handling. The tool has low complexity, but the description is insufficient for an agent to fully anticipate behavior.

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 only parameter, scenePath, has 0% schema description coverage. The tool description implies it is a file path to a KeyShot scene, but provides no additional details on path format, requirements, or typical values. This adds minimal value beyond the parameter name.

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 that the tool opens a KeyShot scene and returns objects, cameras, materials, and metadata. The verb 'inspect' aligns with this, distinguishing it from sibling tools that modify or render scenes. However, it does not explicitly differentiate from siblings, leaving some ambiguity.

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 like keyshot_apply_material or keyshot_render. There is no mention of prerequisites, such as requiring a scene to be open or the file format of scenePath.

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