list_patterns

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the basic operation (listing patterns) and filtering, but lacks details about output format, sorting, or side effects. The presence of an output schema mitigates this somewhat, but the description could elaborate on return structure.

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 extremely concise with only two sentences and an argument list. It immediately states the main purpose and provides necessary parameter details without any fluff.

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 listing tool with one optional parameter, the description covers the core functionality. It could be improved by mentioning the order of results or what information is returned (e.g., names, metadata), but the presence of an output schema likely fills this gap.

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 description fully explains the single parameter 'category', including its purpose, an example value ('drums'), and the behavior when left empty. This adds significant value beyond the schema, which has no descriptions and 0% coverage.

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 'List saved patterns in the pattern library,' specifying the action (list) and the resource (saved patterns). It is distinct from sibling tools like list_songs and load_pattern, making its purpose unambiguous.

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 explains the optional category parameter and its default behavior, guiding usage. However, it does not explicitly contrast when to use this tool versus alternatives (e.g., list_songs), though the resource distinction is clear from names.

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