Get FDA / Compounding Regulatory Status

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

Annotations already declare readOnlyHint=true. The description adds value by enumerating the returned data (approval status, schedule, pathway, uses, off-label note), giving the agent a clear picture of output beyond the schema.

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 sentences cover input, output, and importance. No extraneous details; each word serves a purpose. Properly front-loaded for quick consumption.

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 single-parameter tool with no output schema, the description lists all major output categories. 'Reference pointers' is slightly vague, but overall it provides enough context for appropriate use among siblings.

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% with a clear parameter description. The description reinforces the acceptable input types (name, id, brand/alias) but adds little beyond what the schema already provides.

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 specifies the action: given a compound identifier, returns FDA status, DEA schedule, compounding pathway, and other regulatory info. It clearly distinguishes from siblings like get_medication_list or get_dosing_protocol by focusing on regulatory/compliance data.

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 phrase 'Essential for compliant compounded-medication practice' clearly indicates when to use (for regulatory compliance). While it doesn't explicitly exclude other tools, the sibling names and unique purpose provide sufficient context.

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