list_patterns

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

No annotations are provided, so the description must carry full behavioral disclosure. It merely states the action without specifying whether it is read-only, what the return structure is, or how the domain filter behaves (e.g., exact match, case sensitivity).

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 a single concise sentence that communicates the main function and optional filter. No unnecessary words or repetition.

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, the description covers the essential action and the optional filter. However, with no output schema and no annotations, it would benefit from mentioning the return type (e.g., list of pattern names) or any pagination/ordering behavior.

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 only provides a domain parameter with a default of null and no description. The description adds that the domain filter is optional, clarifying the param's purpose, but does not detail accepted values or filtering semantics.

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 lists available agentic patterns, with an optional domain filter. It distinguishes from sibling tools like get_pattern (retrieves a single pattern) and add/remove custom pattern tools.

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 implies the tool is for listing patterns and shows that domain is an optional filter. However, it does not explicitly state when to prefer this over alternatives like get_pattern or list_protocols, nor does it mention exclusions.

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