get_design_patterns

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

With no annotations provided, the description carries the full burden. It implies a read-only operation through 'Browse' and 'Returns: Dictionary', and discloses the return format. It does not mention side effects, but none are expected for a catalog lookup.

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 well-structured with headers but contains redundancy: the 'WHEN TO USE' bullets largely overlap with 'USEFUL FOR'. It could be condensed without losing meaning, but the organization aids scanning.

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, simple catalog tool, the description comprehensively covers purpose, use cases, and return value. Since there is no output schema, the explicit 'Returns: Dictionary' note is valuable and complete.

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 and schema coverage is 100%, so parameter descriptions are unnecessary. The baseline for 0-param tools is 4, and the description adds no conflicting or missing information.

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 'Browse the catalog of available design patterns and architectural approaches' with a specific verb and resource. It distinguishes itself from sibling tools like analyze_architecture and get_architecture_recommendation by focusing on a reference catalog rather than analysis or recommendation.

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?

Provides an explicit 'WHEN TO USE' list covering design, learning, evaluation, best practices, and architectural decisions. It lacks explicit exclusions or alternatives, but the context is clear and sufficient for this simple tool.

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