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

Annotations already convey read-only, idempotent, open-world behavior. The description adds valuable behavioral detail beyond annotations by stating that multiple identifiers are AND-matched on the same product, which tells an agent how combinations of parameters are interpreted. It does not cover pagination edge cases, but the output schema and parameter descriptions fill most gaps.

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 tight sentences with no wasted words. The first sentence front-loads the action and the accepted identifier types, and the second sentence adds the key AND-matching semantic. Every clause contributes useful information.

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 description is complete enough for selection and invocation given the rich parameter schema, output schema, and read-only/idempotent annotations. The only notable omission is explicit guidance on when to choose this tool over the UPC-only or image-based sibling tools, but that does not prevent correct use of this tool.

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 100%, so the schema already documents each parameter individually. The description adds relational meaning that the schema cannot capture: multiple identifiers are AND-matched on the same product, and the identifiers are described as 'extracted', indicating they likely come from an upstream extraction process.

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 action ('Search recalls') and the resource (recalls by identifiers), then enumerates the accepted identifier types: UPC, lot code, model number, and product name. This distinguishes the tool from siblings like search_product_recalls_by_upc and search_product_recalls_from_image, even though it does not name them explicitly.

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 implies the tool is for searching when extracted identifiers are available, but it gives no explicit when-to-use or when-not-to-use guidance and does not mention alternatives such as search_product_recalls_by_upc for UPC-only lookups or search_product_recalls_from_image for image input. The context is clear enough to infer usage, but not spelled out.

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