add_audio_player

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

No annotations are provided, so the description must disclose side effects, failure modes, or requirements. It only states the action without explaining whether it overwrites existing nodes, requires a valid parent path, or sets defaults for unspecified parameters. This leaves the agent uninformed about important behavioral aspects.

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, clear sentence with no filler words. It efficiently communicates the core action and is appropriately brief for a tool that still lacks necessary detail elsewhere.

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 11 parameters, no annotations, and no output schema, a one-line description is wholly inadequate. The agent has no information about parameter relationships, type-specific behaviors, or expected return values, making the tool difficult to use correctly.

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 has 11 parameters with 0% coverage from the description. The description does not explain the meaning or purpose of any parameter, including ambiguous ones like unit_size and attenuation_model. This is a complete failure to aid parameter understanding.

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 the specific verb 'Add' and names the exact resource types (AudioStreamPlayer, AudioStreamPlayer2D, AudioStreamPlayer3D) and the target context ('under a parent node in the edited scene'). This clearly distinguishes it from generic node tools like add_node.

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 add_node or batch_add_nodes. It does not mention any prerequisites, exclusions, or conditions that would help an agent choose this tool over the generic add_node.

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