load_item_to_return

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

No annotations are present, so the description carries full burden. It describes the action and parameters but does not disclose side effects, whether existing devices are overwritten, if permissions are needed, reversibility, or return behavior. This is a mutation tool with meaningful behavioral ambiguity.

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 compact and well-structured: one sentence states purpose, followed by a concise parameter list. No wasted words, and the most important information is front-loaded.

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 two-parameter tool with no output schema or annotations, the description covers the core essentials: action, target, parameter semantics, and URI acquisition. Minor gaps remain around error conditions or whether the operation replaces/adds to existing chain devices, but it is largely sufficient.

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 coverage is 0%, but the description fully compensates by explaining both parameters: return_index identifies the target return track, and uri is the browser item URI sourced from browse_path or search_browser. This adds critical meaning beyond the bare schema.

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 states a specific action ('Load a browser item (effect) onto a return track by URI') with clear verb and resource targets. It distinguishes itself from siblings like load_item_to_track and load_instrument_or_effect by explicitly mentioning 'return track'.

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?

Clear context is provided: this is used when the target is a return track, and the URI should originate from browse_path or search_browser. It doesn't explicitly list alternatives or exclusions, but the sibling names make the distinction obvious.

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