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 but does not cover critical aspects like whether this is a read-only or destructive operation, permission requirements, error handling, or side effects (e.g., if loading replaces existing content). This leaves significant gaps for an AI agent to understand the tool's behavior.

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, bulleted list of parameters with brief explanations. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 that there is an output schema (which reduces the need to describe return values) and no annotations, the description covers the basic purpose and parameters adequately. However, for a tool that likely involves mutation (loading onto a track), it lacks details on behavioral traits, error conditions, and integration with sibling tools, making it minimally viable but incomplete.

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 format. Since schema description coverage is 0%, this compensates well by clarifying parameter purposes beyond the bare schema, though it could provide more detail on valid ranges or constraints.

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 distinguish this tool from sibling tools like 'load_drum_kit', which might have overlapping functionality, so it misses the top 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, such as 'load_drum_kit' or other track-related tools. It lacks context on prerequisites, constraints, or typical scenarios, offering only basic parameter explanations without usage context.

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