list_animations

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 disclosure, but it only states what it lists without explaining return format, default behavior (e.g., whether it scans all scenes), or any side effects. This is insufficient for an agent to predict the tool's output or side effects.

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 with no unnecessary words. It front-loads the purpose effectively. However, it is so brief that it omits useful details, but for a simple list tool this level of brevity is acceptable.

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 description lacks an output schema and annotations, so it should explain return values and the effect of the optional 'scene_path' parameter. It does not, leaving critical gaps about what exactly is listed (names, paths, resources) and how filtering works. The description is not complete for confident invocation.

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 schema provides 100% coverage for the single parameter 'scene_path' with a clear description. The tool description adds no extra parameter meaning, so it meets the baseline for high schema coverage without compensation.

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 action ('List') and the resource ('AnimationPlayers and animations'), which distinguishes it from read or create operations like 'read_animation' and 'create_animation'. However, it lacks explicit mention of alternatives or scope nuances, so it does not fully stand out from siblings.

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 provides no guidance on when to use this tool versus alternatives such as 'read_animation' or 'list_all_signals'. There are no exclusions, prerequisites, or context given, leaving the agent to infer appropriate usage from the verb and schema.

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