List all cameras in a 3ds Max scene with their names, classes, and positions. Use pagination parameters to control the result set.
列出场景所有相机：名称、类名、位置。结果分页。 [English] List every camera in the scene: name, class and position. Paginated.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 最多返回条数，默认 200。 | Maximum entries, default 200. | |
| offset | No | 起始偏移，默认 0。 | Starting offset, default 0. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only and non-destructive, and the description adds useful behavioral context: results are paginated and include specific fields. It does not contradict the annotations.
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 compact and front-loaded: it states the purpose, the exact data returned, and the pagination behavior in two short bilingual lines. No filler or irrelevant detail is present.
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 list operation with annotated read-only safety and fully documented pagination parameters, the description is nearly complete. It could optionally specify the exact output shape or empty-result behavior, but none of that is critical for calling the tool.
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 coverage is 100%, with limit and offset already documented including defaults. The description only reinforces pagination without adding new parameter-level semantics, so the schema carries the weight.
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?
Description uses a specific verb and resource: 'List every camera in the scene', and names the returned fields (name, class, position). It clearly separates this from sibling camera tools like cam_get or cam_set by emphasizing enumeration of all cameras.
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 clearly establishes the context: use this tool when you need every camera in the scene, not a single camera's details. It does not explicitly name alternatives or exclusions, but the scope is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.