browser_load_item

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

Discloses idempotency and best-effort behavior, explains return values (changed=true/false with item info). No annotations exist, so description carries full burden; covers key behavioral traits without mentioning error handling.

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?

Only two sentences, front-loaded with main action, then details. Every sentence adds value with no redundancy.

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 no output schema, description fully explains return behavior. Covers purpose, usage context, parameter meaning, and behavioral traits adequately for a simple tool.

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?

Single parameter 'path' is fully described in schema (100% coverage). Description adds value by explaining its use in the context of browser navigation and the types of items loaded.

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?

Description clearly specifies the verb (Load), resource (Ableton Browser item), and context (onto selected/armed track). It lists example item types and distinguishes from sibling tools like browser_get_categories.

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?

Explicitly states to use after browser_get_categories/path discovery, providing clear sequential context. Does not include explicit when-not-to-use but the context is sufficient.

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