load_instrument_or_effect

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

With no annotations, the description carries the full burden. It only states the basic action and parameters, but fails to disclose side effects (e.g., overwriting existing devices), required track state, or destructive behavior. The agent gets no insight into what happens beyond the load.

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 concise (two sentences), front-loads the purpose, and includes only essential information. It is well-structured and avoids verbosity, though the parameter list could be formatted more cleanly.

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 tool with 3 parameters (one standard), no output schema, and no annotations, the description covers the basic operation and parameter syntax. However, it lacks details on return values, error conditions, and behavioral consequences, making it minimally adequate for a context-aware agent.

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%, so the description must compensate. It explains both 'track_index' and 'uri' with an example URI, adding meaningful context beyond the schema's type-only definitions. The 'ctx' parameter is not described, but it is a standard framework injection and omission is acceptable.

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's action ('Load'), target ('instrument or effect onto a track'), and method ('using its browser URI'). It distinguishes itself from siblings like 'load_drum_kit' and 'load_browser_item' by specifying the content type, though it does not explicitly contrast them.

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 like 'load_browser_item' or 'load_drum_kit'. It does not mention prerequisites, when not to use, or any exclusion criteria.

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