Product forms

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely useful context beyond that: the corpus size (~360 forms) and the default listing behavior when `query` is omitted. It does not mention the 60-item cap or pagination, which is a minor gap.

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?

Two short sentences with the core purpose and downstream usage front-loaded, plus one line of scale context. The "from tablets to thermometers" flourish is mildly decorative but reinforces that forms include non-pharmaceutical items, so it mostly earns its place.

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 only two optional parameters, no nesting and no output schema, the description covers what an agent needs: what it returns (form ids), how to filter, and how the output feeds dr_search. A brief note on the response shape or the 60-item limit would make it fully self-sufficient.

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%, so both parameters are already documented, and the baseline would be 3. The description goes further by explaining what the returned ids are *for* downstream (the `form` argument of dr_search) and by restating the default listing behavior, which the schema's `query` default of null only implies.

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 and resource ("List product forms") and immediately defines the output as the ids that dr_search accepts as `form`. It also names concrete examples (capsule, tablet, syrup) that distinguish it from siblings like dr_categories or dr_brands.

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?

Gives an explicit two-step workflow: find the form id here, then call dr_search(query, form=[id]) with examples like "vitamin D drops" and "melatonin capsules". It also covers the no-query case ("the first forms are listed"), so both invocation modes are explained.

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