get_kr_pharma_pipeline

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

With no annotations, the description must disclose behavioral traits, but it only states the ranking criterion. It does not mention what the overview contains, how phases are handled, whether the data is current, or any default limits. This is insufficient for a tool that likely accesses a data source.

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 that directly conveys the tool's primary purpose. It is front-loaded and contains no filler or redundant information, making it highly efficient.

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?

The tool is simple, but the description lacks essential context such as what data is actually returned, how the 'phase' filter works, and what the default ranking count is. Without an output schema, the description should compensate, but it does not.

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 0% and the description does not mention the 'top' or 'phase' parameters at all. The parameter names are somewhat self-explanatory, but the description adds no meaning beyond the bare schema, leaving the agent to guess at allowed values and behavior.

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 clearly indicates the tool returns an overview of the Korean pharma pipeline ranked by active clinical trials, which is specific enough to infer the core function. However, it does not explicitly distinguish itself from sibling tools like search_pharma_trials or get_upcoming_catalysts, so it misses the 5-level differentiation.

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 provides no guidance on when to use this tool versus alternatives, such as search_pharma_trials for granular trial details. There is no mention of prerequisites, typical use cases, or exclusion criteria, leaving the agent without context for tool selection.

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