get_upcoming_catalysts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List' and does not explain side effects, permissions, rate limits, or return behavior. Although it implies a read-only operation, it omits details like whether specific parameters are required or what the output format looks like.

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, clear sentence that directly states the tool's function without unnecessary fluff. It front-loads the key action and resource. However, it is slightly under-specified for a tool with three parameters, but this is not a conciseness issue; the sentence itself is well-structured.

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 the tool has 3 parameters, no annotations, and no output schema, the description is too minimal to be fully complete. It explains the general purpose but leaves parameter meanings and expected response undefined. The description is adequate for a basic understanding but lacks necessary context for correct 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 input schema has 3 parameters (phase, months, symbol) with 0% schema description coverage, and the description does not explain any of them. It only refers to 'N months' without clarifying the 'months' parameter, and 'phase' and 'symbol' are completely unexplained. The description adds no meaning beyond the parameter names.

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 states the tool's purpose with a specific verb ('List') and resource ('upcoming clinical trial catalysts (completion dates)'), and it narrows the scope to Korean pharma companies within a given time frame. This distinguishes it from siblings like get_kr_pharma_pipeline or search_pharma_trials, which likely cover broader pipeline or trial searches.

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 implies usage by defining the scenario (upcoming catalysts within N months), but it does not explicitly mention when to use this tool instead of alternatives such as search_pharma_trials or get_kr_pharma_pipeline. There are no exclusions or conditional guidance, so the usage context is implied but not explicit.

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