ableton_list_workflow_plans

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

With no annotations, the description bears full burden. It states the output (workflows and risk tiers) but omits behavioral details like whether results are sorted, paginated, or if there are any side effects (though likely read-only). Basic transparency but lacks depth.

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?

A single, focused sentence with no redundant words. It efficiently communicates the tool's purpose without any filler.

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 list tool with no parameters and no output schema, the description is largely complete. However, it could specify the return format (e.g., list of objects) or include units for risk tiers, making it slightly less complete than ideal.

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?

No parameters exist, and the description adds no syntax or format details beyond the schema. The baseline for zero-parameter tools is 4, and the description's mention of 'risk tiers' provides context not in the empty schema.

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 states the tool lists high-level plan-only production workflows and their risk tiers, using the specific verb 'List' and specifying the resource. It distinguishes itself from siblings like 'ableton_get_workflow_plan' which likely retrieves a single plan.

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?

While the description implies use for getting an overview of plans, it provides no explicit guidance on when to use this tool versus alternatives, such as when needing a specific plan detail vs. a summary list.

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