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

No annotations provided, so the description carries the full burden. It hints at read-only/non-deterministic behavior via 'heuristic matcher' and 'suggests', but omits auth requirements, rate limits, side effects, or output characteristics.

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?

One concise sentence, front-loaded with the tool's action. No wasted words, though it could include more specific guidance without becoming verbose.

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?

Tool has 8 parameters, 0 required, 0% schema coverage, no annotations, and a complex heuristic matching purpose. Output schema exists, so return values needn't be described, but the description omits all input semantics and usage 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% across 8 optional parameters (cve, package, rule_id, keywords, ecosystem, facets, min_quality, limit), and the description mentions none of them. It adds no meaning beyond parameter names.

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 states a specific matching action ('suggests best-fit recipes') and target ('security finding'), so an agent can tell it is a matcher. However, it does not differentiate from sibling tools like recipes_cve_search or recipes_playbook_plan, and 'security finding' is undefined.

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 when-to-use guidance, no alternatives, no prerequisites. The description does not say when to choose this over recipes_cve_* or recipes_search.

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