list_scenes

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

With no annotations, the description must disclose behavioral traits. It only states 'list all scenes' without mentioning pagination, ordering, or whether the response is limited. The output schema exists but is not referenced. This is insufficient for full transparency.

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 extraneous words. Every word ('List all animation scenes in the workspace') is necessary and clear. It earns its place without redundancy.

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 tool with no parameters and an output schema, the description is largely adequate. It could optionally mention that the output is a list of scene objects, but the lack of such detail does not hinder understanding given the tool's simplicity.

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 input schema has zero parameters, so the description's statement 'list all' is consistent. There are no parameters to explain, and the description confirms the unconditional nature of the list. Baseline is high due to no parameters.

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 tool lists all animation scenes in the workspace. It uses a specific verb ('list') and a distinct resource ('scenes'), which differentiates it from sibling tools like 'get_scene' (single scene retrieval) and other scene manipulation 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 implies usage for listing all scenes, but provides no explicit guidance on when to use it versus alternatives (e.g., get_scene, search tools). No conditions, prerequisites, or exclusions are mentioned, which is acceptable for a simple list tool but still lacks proactive clarity.

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