Resolve a loose reference (partial id, display_id, slug fragment, or title keyword) to canonical pattern_id(s). Call this when you have a rough reference and need the exact id before calling get_requirement. Always returns candidates — never 'not found'.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
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 discloses that the tool always returns candidates (never 'not found'), which is useful. However, it omits details on response format, error handling, or side effects. For a simple lookup tool, this is adequate but not comprehensive.
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?
Two sentences with no redundancy. The first sentence defines the core action, and the second adds usage guidance and a behavioral note. Every sentence adds value.
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 no output schema, the description does not specify the return structure (e.g., list of IDs, matching metadata). It mentions 'candidates' but lacks detail on format. For a tool with two parameters and simple output, the completeness is moderate but leaves the agent guessing about response shape.
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%, so the description compensates by explaining the query parameter: 'loose reference (partial id, display_id, slug fragment, or title keyword).' However, the limit parameter is not mentioned, leaving its purpose and constraints undocumented.
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 explicitly states the tool resolves a loose reference to canonical pattern_id(s), listing specific input types (partial id, display_id, slug fragment, title keyword). It distinguishes from siblings by mentioning its role as a prerequisite for get_requirement.
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 gives clear context: 'Call this when you have a rough reference and need the exact id before calling get_requirement.' It does not explicitly state when not to use, but the context is sufficient for selecting this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: finding patterns, cross-references, operational heuristics, requirements, listing, searching, and review stats. Overlap is minimal and well-differentiated by input parameters.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., find_patterns_for_task, list_requirements, resolve_id. No mixing of conventions or vague verbs.
12 tools cover core operations (list, get, search, resolve, review) for the framework domain without bloat. Each tool serves a clear, non-redundant purpose.
Covers most needed operations for exploring the framework: listing suites, searching patterns, getting details, cross-references, review stats. Lacks a direct 'list all patterns' tool, but list_requirements and search_patterns partially fill that gap.
