find_pattern

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions patterns are 'verified' which implies curated content, but it doesn't state if the tool is read-only, return format, or any side effects. For a search tool, the read-only nature is implicit but not explicitly stated.

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 two sentences, front-loaded with the purpose, and includes a usage guideline. No redundant information, every word earns its place.

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 search tool with no output schema, the description does enough to identify purpose and usage, but it omits what the search returns (e.g., matching patterns) and parameter details. It's adequate but not rich in context.

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 description must compensate. It provides examples of intents for query (constrained rectangle, etc.) but doesn't explain the exact syntax, what limit controls, or how results are returned. Minimal compensation for undocumented parameters.

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 searches patterns.md for verified Fusion MCP patterns and helpers by intent. It specific verb 'search' and resource 'patterns.md', and it distinguishes from siblings like find_api, find_tool, and find_gotcha by focusing on patterns.

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?

It explicitly says to use when looking for the canonical idiom for a common operation, giving examples (constrained rectangle, fillet by geometry, screenshot fit-view). It lacks explicit when-not-to-use or alternative suggestions, but the context is clear enough.

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