load_instrument_or_effect

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. It states the action ('Load') but does not explain what happens during loading (e.g., whether it replaces existing content, requires specific permissions, or has side effects like mutating track state). This is a significant gap for a tool that likely modifies session data.

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 front-loaded with the core purpose in the first sentence, followed by a clear parameter list with brief explanations. Every sentence adds value without redundancy, making it efficient and easy to parse for an agent.

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?

Given the complexity of loading instruments/effects in a music production tool, the description is minimally adequate. It covers the basic purpose and parameters but lacks details on behavior, output, or integration with siblings. With no annotations or output schema, it leaves gaps in understanding the full context of use.

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 description adds meaningful context for both parameters: 'track_index' is explained as 'The index of the track to load the instrument on', and 'uri' includes an example ('e.g., 'query:Synths#Instrument%20Rack:Bass:FileId_5116''). Since schema description coverage is 0%, this compensates well by clarifying parameter purposes beyond the basic schema types.

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 ('Load an instrument or effect') and the target ('onto a track using its URI'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'load_drum_kit' or 'create_midi_track', which might have overlapping purposes in a music production context, so it falls short of a perfect score.

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. It does not mention prerequisites, such as needing an existing track or valid URI, or compare it to siblings like 'load_drum_kit' or 'create_midi_track', leaving the agent to infer usage context from the tool name alone.

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