list_patterns

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

No annotations are provided. The description merely states the action without disclosing behavioral traits such as whether the result is paginated, sorted, or if there are any limitations. With zero annotations, the description should provide more transparency.

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, concise sentence that conveys the essential purpose. No unnecessary words, and it is front-loaded with the key information.

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 the simplicity (0 parameters, with an output schema), the description is minimally complete but lacks context such as what 'canonical' means or whether the list is ordered. It does not explain the output format, relying on the output schema. Slightly more detail would improve usability.

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 input schema has no parameters. According to guidelines, 0 parameters yields a baseline of 4. The description does not need to add parameter information as there are none, so it adequately fulfills this dimension.

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 tool returns all canonical pattern names. It specifies the verb 'return' and the resource 'canonical pattern names', distinguishing it from sibling tools like 'get_pattern' which returns a single pattern's details.

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 (e.g., get_pattern for details, or other list tools). The description lacks context for an agent to choose correctly among sibling tools.

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