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

With no annotations provided, the description carries the full burden of explaining behavior, but it only says 'Structured clinical intelligence' and 'ingest and distill.' It does not reveal what the tool does with the URL, what kind of structured output is produced, whether any state is persisted, or what side effects may occur. This is far too little behavioral disclosure for an unannotated 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 a single concise sentence with no redundant wording. It is front-loaded with the '[Custom Enterprise Schema]' flag. However, its brevity sacrifices meaningful content, so it is concise in size but not in substance.

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?

Despite having only one parameter, the tool has no output schema, no annotations, and a description that does not specify what the 'distilled' result looks like. An agent cannot confidently determine what data will be returned, how the URL is processed, or how the output is structured. This is incomplete for practical invocation.

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 schema provides 100% coverage for the single 'url' parameter with the description 'Target URL to ingest and distill,' so the schema already explains the parameter adequately. The main description adds domain context ('pharmaceutical and biotherapeutic regulatory milestones') but no parameter-specific usage detail. Since schema coverage is high, a score of 3 is appropriate.

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 is a vague, noun-phrase slogan: 'Structured clinical intelligence for pharmaceutical and biotherapeutic regulatory milestones.' It does not state a specific action like 'extract,' 'analyze,' or 'find drug approvals.' It also fails to differentiate from siblings such as refinery_custom_biopharma_fda_patent_cliffs or refinery_custom_clinical_trials, which could plausibly share the same description.

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?

There is no guidance on when to use this tool versus alternatives. No context is given about suitable input types, desired use cases, or exclusions. The only hint is the parameter description 'Target URL to ingest and distill,' which implies a fetch-and-extract workflow but does not explain when this tool is the right choice.

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