toggle_browse

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

With no annotations, the description carries the full burden. The verb 'toggle' discloses a state flip, and the phrase 'for the selected device' implies a prerequisite. However, it does not explain what happens if no device is selected, whether the operation is idempotent, or any side effects. The output schema covers return values, but this behavioral context is minimal.

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 a single, clear sentence with no redundant words. It is front-loaded with the action and resource, making it easy to scan.

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 simple toggle tool with no parameters and an output schema, the description is sufficient. It clearly names the action and target. It could add context about integration with browser workflows, but that is not necessary for basic selection.

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 tool has zero parameters, so there is nothing to explain. The description correctly omits parameter details, and the baseline of 4 applies for no-parameter tools.

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 ('toggle') and the specific resource ('Ableton's browser hot-swap mode') scoped to 'the selected device.' This precise wording distinguishes it from other toggle tools like toggle_presentation_mode.

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 implies usage when wanting to toggle hot-swap mode for a selected device, but it lacks explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, and prerequisites are only hinted at via 'for the selected device.'

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