inspect_animation_players

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

With no annotations, the description carries the full burden. 'Inspect' implies a read-only operation, but the description does not disclose what is returned (e.g., list of animations or properties), whether it reads from the scene file or live scene, or any limitations. This is minimal behavioral 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 concise sentence with no fluff. It front-loads the key action and resource, making it easy to parse. No unnecessary words are 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?

This is a simple tool with no output schema and no annotations, but the description is still too sparse. It omits parameter semantics, return format, and usage context, leaving the agent without enough information to confidently invoke the tool. Given the low complexity, more detail is expected.

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 50%, with only projectPath having a description. The tool description does not explain the required scenePath parameter, its format, or how it relates to the operation. Since the description adds no meaning beyond the bare schema, it fails to compensate for the gap.

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 inspects AnimationPlayer nodes and animation names, using a specific verb ('Inspect') with a concrete resource. It distinguishes itself from generic siblings like inspect_node and inspect_scene_tree by specializing in AnimationPlayer nodes.

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 when the agent needs to inspect AnimationPlayer nodes or animation names, but it does not explicitly state when to prefer this over alternatives like inspect_node. No prerequisites or exclusions are mentioned, but the specialized purpose provides some guidance.

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