analyze_existing_patterns

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the purpose and argument, omitting side effects, permissions, or output characteristics. The tool implies mutation? No, it's analysis, but nothing about idempotency or impact.

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 concise with two sentences, front-loading the purpose. Every sentence adds value, though it could briefly mention the output to improve completeness without harming conciseness.

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?

The tool has an output schema (unknown content), so return values may be covered there. The description is adequate for a single-parameter analysis tool but lacks hints about the output structure (e.g., a list of patterns) or behavioral details, leaving some gaps.

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 only parameter 'test_suite_path' has a schema description coverage of 0%, but the description adds 'Path to a `suite_*` directory.', which clarifies the expected format beyond a generic string. This provides useful semantic context, though no further constraints are given.

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 verb 'Analyze' and the resource 'test suite' to find 'common patterns' for generating new test cases. It distinguishes from sibling tools like 'analyze_bdd_context' by focusing on pattern extraction, though the differentiation is implicit.

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 vs alternatives, such as other analyze tools or pattern-related functions. The description does not mention prerequisites or context.

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