pattern_list

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

The description discloses the return structure directly, which is useful since no annotations are provided. It does not explicitly state that the operation is read-only, nor does it mention ordering, pagination, or empty-list behavior, so transparency is adequate but not rich.

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 sentence that front-loads the action and object, then gives the compact return shape. Every element is useful and there is no 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 zero-parameter read-only query, the description is complete: it says what the tool returns and in what structure. No output schema exists, so including the element fields in the description is necessary and sufficient.

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?

There are zero parameters, so the input schema imposes no documentation burden. The description adds value by specifying the return fields, which is the only semantic information needed here.

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 ('Return'), a clear resource ('all patterns'), and the exact shape of the returned items. This distinguishes it from sibling tools like pattern_count or pattern_current by indicating it returns a full list rather than a count or a single current pattern.

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 intended use is implied by the phrase 'all patterns' — the tool should be used when full enumeration is needed. However, there is no explicit guidance about when not to use it or which alternative to choose for more targeted queries.

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