list_cameras

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

With no annotations provided, the description carries the full burden of behavioral transparency. It simply says 'List Camera nodes' without disclosing whether the operation is read-only, what information is returned, whether hidden nodes are included, or what happens if no scene is open. Minimal behavioral context is provided beyond the implied read-only nature of 'list'.

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, focused sentence with zero extraneous words. It is concise without being under-specified for the tool's simplicity, setting a good example of minimalism.

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 simple (one optional parameter, no nested objects, no output schema), so the description is adequate in that sense. However, it does not mention the return format or any caveats (e.g., whether nodes from all scenes are returned by default). For a list operation without an output schema, some hint about the return value would improve completeness.

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 100% (the only parameter has a clear description: 'Filter to a specific scene (default: all scenes)'). The description adds no extra parameter semantics, but the baseline of 3 applies because the schema already documents the parameter effectively. The default 'all scenes' is a useful detail.

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 'List Camera nodes' clearly states the action (list) and the resource (Camera nodes), distinguishing it from sibling tools like list_lights or list_materials. However, it lacks explicit scope clarification (e.g., current project vs. scene), though the parameter description partially fills this gap. It earns a 4 because it is specific but not as richly differentiated as examples that explicitly state scope or alternatives.

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 guidance on when to use this tool versus alternatives such as list_scenes or read_camera. The parameter description mentions filtering by scene but does not explain use cases or exclude scenarios. This is a clear gap for a tool that could be confused with other list/read operations.

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