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

No annotations are provided, so the description carries the full burden. It discloses the paid nature (cost, blockchain), the ranked output, and the components (expiry, recalls, supplier screen). It also explains the free preview behavior. This is fairly transparent for a complex report tool.

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 concise, fitting essential information into two sentences. The first sentence packs the payment detail, purpose, and contents. The second covers the free caller case. No superfluous words.

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 tool with 2 well-documented parameters and no output schema, the description covers the report's components and payment model. It might lack detail on the output format or error conditions, but given the simplicity, it is sufficiently complete.

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 coverage is 100%. The description adds the hint to use list_categories for the category parameter, but otherwise the schema already describes both parameters adequately. The description does not provide additional semantic value beyond the schema.

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 it produces a full off-patent opportunity report for a category slug, listing specific contents (design patents, expiry, safety screens, rankings). This is distinct from siblings like list_categories (just lists slugs) and newly_expirable (likely different focus).

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 indicates payment requirement and mentions free callers get a preview, which implicitly tells when to use the paid version. It references list_categories for obtaining the slug, providing a prerequisite. However, it does not explicitly compare to siblings or state when not to use this tool.

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