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

No annotations are provided, so the description carries full burden. It fails to disclose whether criteria are combined with AND/OR logic, whether the operation is read-only, pagination behavior, or what constitutes a valid search (e.g., minimum criteria requirements). The agent receives no behavioral context beyond the basic function.

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, efficient sentence with no redundant words. It is appropriately front-loaded with the action ('Search clinical trials') and immediately qualifies the scope ('using multiple criteria').

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 8 parameters, no annotations, no output schema, and numerous specialized siblings, the description is incomplete. It omits critical context: all parameters are optional (required: 0), the relationship to single-criterion siblings, and how results are structured or limited (beyond max_studies default).

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?

With 100% schema description coverage, all parameters are already well-documented in the structured schema. The description lists some parameter categories but adds no semantic value beyond what's in the schema (e.g., no syntax examples, no explanation of 'fields' vs 'terms'). Baseline 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 clearly states the tool searches clinical trials using multiple criteria and lists the primary filter types (conditions, interventions, sponsors, terms, NCT IDs). However, it does not explicitly contrast this combined approach with the single-criterion sibling tools (search_trials_by_condition, etc.), which would help the agent understand the 'combined' 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 multi-criteria tool versus the specialized single-criterion alternatives (search_trials_by_sponsor, search_trials_by_condition, etc.). Given the abundance of siblings, explicit guidance like 'Use when filtering by multiple criteria simultaneously' is missing.

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