Retrieve the list of 3D scenes accessible to your authenticated Cartwheel account, with optional limit, pagination, and sorting to manage results.
Retrieves scenes available to the authenticated service account.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of scenes to return | |
| nextToken | No | Pagination token from a previous response | |
| sortAscending | No | Sort results in ascending order by creation time |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description only needs to add behavioral context. It adds the scoping detail of the authenticated service account, but does not mention pagination, sorting, or response format.
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, front-loaded sentence with no wasted words. It states the verb, resource, and scope efficiently, which is entirely appropriate for a simple list operation.
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?
With no output schema, the description does not describe what fields a scene contains or how results are returned. The input side is well-covered by the schema, but an agent may be left uncertain about the response structure for this list operation.
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%, with all three optional parameters (limit, nextToken, sortAscending) documented in the input schema. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.
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 uses a specific verb ('Retrieves') and resource ('scenes'), and adds a clear scope ('available to the authenticated service account'). This makes it immediately distinguishable from siblings like get_scene (singular retrieval) and search_motions (searching a different resource).
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 explicit guidance is given about when to use this tool instead of alternatives such as get_scene, search_motions, or list_motions. Usage is only implied by the plural resource name and straightforward list semantics, with no exclusions or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.