garageband_export_song

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

No annotations are provided. The description implies GUI automation ('by driving GarageBand's export dialog'), but fails to disclose potential side effects like blocking behavior, dialog state changes, or error conditions. The description does not add behavioral context beyond what is inferred.

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 sentence, which is very concise. However, it could be slightly more structured to improve readability, such as separating the action from the mechanism.

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 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the output file location, naming convention, or success verification, leaving the agent with many uncertainties.

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 has 0% description coverage, and the tool description adds no explanation for parameters like 'quality', 'include_cycle', 'overwrite', or 'timeout_seconds'. The enum values for 'format' are self-explanatory, but the description provides no additional meaning for any parameter.

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 ('Export'), the resource ('current GarageBand song'), and the target formats (AAC, MP3, AIFF, or WAVE), distinguishing it from sibling tools like garageband_export_dialog which likely just opens the dialog.

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?

No guidance on when to use this tool versus alternatives, such as garageband_export_dialog. It also does not specify prerequisites (e.g., a song must be open) or when to prefer one format over another.

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