Fl Patterns

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return contents including the 1-based indexing convention, selected flag, groups, and current pattern — useful context beyond a bare 'list patterns.' It doesn't describe timing or live-state behavior, but for a zero-parameter read tool this is largely sufficient.

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 compact sentence that front-loads the verb and packs the entire return contract into a tight parenthetical list. No wasted words.

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?

With an output schema present, return-value structure is already covered. The description adds the 1-based indexing note and scope (patterns, groups, current pattern), which is complete for a stateless query tool with no parameters.

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 per calibration this receives the baseline 4. There is no parameter ambiguity to resolve.

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 states a specific verb (List) and resource (patterns), and enumerates the exact fields returned (name, length in beats, colour, selected; groups; current pattern). This clearly distinguishes it from mutation siblings like fl_pattern_create and fl_pattern_set.

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 verb 'List' makes the read-only intent self-evident, and the explicit mention of what data is returned clarifies when to call it. The contrast with fl_pattern_create and fl_pattern_set is implied by the enumerative nature, though no explicit when-not-to-use guidance is given.

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