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

Annotations already mark this as read-only and idempotent. The description adds valuable behavioral context beyond those hints: it covers historical notices, clarifies that generic patterns match only in titles, and states that notifications are not created. It also flags the API key requirement. No contradiction with the annotations exists.

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 four short sentences with front-loaded purpose. Every sentence contributes useful information—scope, side-effect denial, matching behavior, and authentication requirement—with no redundant fluff.

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?

This is a simple two-parameter read-only tool, and the description covers scope, auth, matching semantics, historical inclusion, and side effects. The return shape is implied by 'check ... against recalls' plus the pagination parameters, so an agent has enough context to 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?

The input schema already fully documents both parameters (limit and offset) with clear descriptions, defaults, and ranges. The tool description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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—'Check this API key's watch patterns and inventory against current indexed recalls'—and clearly identifies the resource and scope. It also distinguishes itself from notification-related tools by explicitly saying it does not create notifications, which helps separate it from siblings like list_recall_notifications.

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 for when to use this tool: when you want to evaluate an API key's tracked watch patterns and inventory against recalls. It names a prerequisite (API key) and notes that generic patterns only match in titles, but it does not explicitly point to alternative tools like search_product_recalls for unrelated recall searches.

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