load_browser_item

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'loads' an item onto a track, implying modification, but does not describe potential side effects (e.g., replacement, permission requirements, handling of invalid URIs). More transparency is needed.

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 two sentences, front-loading the purpose and then adding usage guidance. It is efficient with no wasted words, though it lacks parameter documentation.

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 tool has three required parameters and no output schema or annotations, the description is insufficient. It does not explain return behavior, prerequisites (e.g., track existence, URI validity), or how to interpret potential errors.

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 description coverage is 0%, and the description does not explain any of the three parameters (ctx, item_uri, track_index). The description adds no meaning beyond the raw schema, leaving the agent without necessary context for parameter values.

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 loads any browser item onto a track by URI, and explicitly distinguishes itself from load_instrument_or_effect by specifying it's for non-instrument/effect items like samples. The action and resource are specific.

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 explicit guidance on when to use this tool (for browser items that aren't instruments or effects) and names the alternative tool (load_instrument_or_effect). It does not cover all sibling alternatives but gives clear context for the primary distinction.

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