react_list_patterns

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

No annotations are provided, so the description carries the full burden. It declares a read operation (list) but does not disclose pagination, rate limits, or the meaning of 'by category' (e.g., whether it returns all patterns if no category is given). Adequate but not detailed.

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 8-word sentence that is front-loaded and contains no fluff. Every word earns its place, making it efficient for an agent to parse.

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 tool with one optional enum parameter and no output schema, the description is mostly sufficient. It covers the basic function but could mention the output format (e.g., returns a list of pattern objects) to be fully 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?

Schema description coverage is 0%, and the description only adds 'by category' which maps to the category parameter. It does not explain the enum values (e.g., what 'rendering' includes) or that the parameter is optional. Minimal value added beyond the schema.

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 'List all React/Next.js patterns by category' clearly states the action (List), resource (React/Next.js patterns), and scope (by category). It distinguishes from sibling tools like react_get_pattern (single pattern) and reactflow_list_apis (different framework).

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 usage for listing patterns with an optional category filter but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Given the many sibling list tools, more context would help.

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