generic-timeline

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

With no annotations, the description carries full disclosure burden and meets it: it explains the NADAC price-dispersion methodology, the conditional output (price range vs. expiry), the explicit rule never to present patent expiry as a launch date, and the handling of pediatric exclusivity. It effectively tells the agent what the tool will and will not do.

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 about 100 words and every sentence contributes to the purpose, methodology, or a caution. It is slightly longer than strictly necessary, but the explanatory reasoning about why FDA approval counts are insufficient adds useful context.

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?

Given no output schema or annotations, this description does almost everything required: it specifies the input domain, the decision rule, the two output cases, and an important edge case (pediatric exclusivity). An agent can predict the tool's behavior and results without further structured metadata.

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 single parameter is fully described in the input schema with name and example values, so the description adds no further parameter-specific semantics. The tool description's mention of 'NDCs of one drug identity' relates indirectly, but the schema alone provides enough for correct invocation.

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 opens with a specific verb and resource ('report whether a real MARKETED generic exists today' for a US prescription drug), and immediately distinguishes its market-based criterion from FDA approval counts. It also declares the two possible return outcomes, so an agent knows exactly what the tool produces.

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 clearly implies when to use it – whenever true marketed generic status is needed – and explains why not to rely on FDA approval counts. It does not name an explicit alternative tool, but given no siblings are provided, the context is sufficient and the exclusion is conceptually stated.

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