topai_pharmapatent_watcher

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the closing line 'Stateless, read-only, idempotent lookup' largely restates them, earning no additional credit. The description does add data-provenance context (FDA Orange Book, European exclusivity), but says nothing about rate limits, auth requirements, or data freshness for an open-world external lookup.

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?

Three sentences, front-loaded with the returned data, followed by usage scoping and the safety profile. Every sentence carries distinct information and there is no filler.

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?

With no output schema, the description enumerates the return payload (cliff dates, ingredient metadata, exclusivity expirations, threat levels), so return semantics are covered. Inputs, exclusions, and safety profile are all present; nothing needed to invoke it correctly is missing.

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% and the enum on jurisdiction is fully documented in the schema, so the baseline is 3. The description does not add format, defaulting, or matching semantics (e.g., brand vs. generic resolution) beyond what the schema already states.

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?

States a specific verb (Retrieves) and a precisely scoped resource set: patent cliff dates, active ingredient metadata, Orange Book/EP exclusivity expirations, and generic entry threat levels for a named drug. This is clearly distinguishable from every sibling, and it even names the healthcare_validator it is not.

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?

Explicitly names the use cases (life-sciences competitive intelligence, LOE forecasting, pharma IP analysis) and gives an exclusion with a redirect: 'Do not use for verifying individual physician NPI medical licenses (use topai_healthcare_validator instead).' Both the when and the when-not are stated.

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