save_set

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

With zero annotations the description carries the full load and does well: it discloses the mutation ('invokes Song.save()'), that it happens 'in one undo step', that require_api=True raises on a missing API, and that a missing API otherwise yields a structured GUI workflow. It omits permission/auth requirements and what a save overwrites, keeping it short of a 5.

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?

Front-loaded with the core purpose, then side effects, example, and edge cases in labeled blocks. Efficient overall, though the 'Edge cases' line partly restates the opening 'otherwise return a GUI workflow', a minor 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?

For a one-parameter, no-annotation, no-output-schema mutation tool, the description covers purpose, side effects, parameter behavior, and failure modes. Remaining gaps (shape of the GUI workflow response, permission requirements) are minor for this scope.

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 coverage is 0% for the single parameter, so the description must compensate; the example 'save_set(require_api=True) raises when the API is missing' plus the default-path GUI behavior together explain both the true and false semantics of require_api. The default value itself is only in the schema, not restated in prose.

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?

States a specific verb+resource ('Save the Live Set') and immediately distinguishes the two execution paths (Song.save() vs GUI workflow). No sibling tool performs a session save, so an agent can pick this out unambiguously.

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?

It explains the internal branch (API vs GUI) and shows a call example, which implies usage, but never states when an agent should prefer save_set over anything else or what preconditions must hold. No explicit when-to-use / when-not-to-use guidance is present.

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