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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Heuristic matcher' hints at non-deterministic or best-effort matching, and 'suggests' implies a non-mutating action, but it does not disclose any side effects, authorization needs, rate limits, or the nature of the matching process.

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 a single, front-loaded sentence with no redundant wording, so it is concise. However, one short sentence is too sparse for a tool with eight parameters and many sibling tools, leaving substantial coverage gaps.

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?

A return schema exists, so the description need not explain outputs, but it omits all parameter semantics, usage context, and behavioral caveats. For a heuristic matching tool with eight optional inputs and a large sibling set, this is not enough for an agent to confidently select and invoke it correctly.

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 mentions none of the eight parameters (cve, limit, facets, package, rule_id, ecosystem, min_quality). The description provides zero additional meaning to help an agent understand what each parameter controls or how to combine them.

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 action ('suggests best-fit recipes') and a clear target ('security finding'), so an agent can identify its core function. It does not explicitly contrast with sibling tools like recipes_cve_search or recipes_mcp_upstream_tools, so differentiation is partly left to inference.

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?

There is no guidance on when to use this tool versus the many recipe-related siblings, nor any excluded cases or alternative suggestions. The phrase 'for a security finding' implies the general context but does not define when this matcher is preferable to direct search or retrieval tools.

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