search_trials

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool searches and returns fields, which implies a read operation, but it does not state read-only behavior, authentication needs, rate limits, or pagination/default-limit behavior. For a search tool with zero annotations, these gaps matter.

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?

Three short sentences front-load the main capability, then list filters, then summarize returned fields. Every sentence contributes useful information, and there is no filler or repetition.

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?

An output schema exists, so returned fields need not be fully explained, and the description still names key return fields. But with six optional parameters and no annotations, it should ideally cover `limit`/pagination and clarify search-combination semantics. It is adequate for basic invocation but incomplete for fully informed use.

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%, so the description must compensate, and it does add meaning for condition, intervention, sponsor, status, and phase, including status and phase examples. However, it omits the `limit` parameter entirely and does not clarify whether condition, intervention, and sponsor are combined with AND or OR logic.

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 states a specific verb and resource: search ClinicalTrials.gov trials by condition, intervention and/or sponsor. It also names filters and returned fields, so the core purpose is clear. However, it does not explicitly distinguish this search tool from the sibling `get_trial`, leaving some sibling differentiation implicit.

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 the tool is for searching trials by condition, intervention, sponsor, status, or phase, but it gives no explicit when-to-use guidance. It also does not mention when to use `search_trials` instead of `get_trial` or other sibling tools, so an agent must infer routing.

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