clinical_trials_enums

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that it returns every enum type with all valid values, which is helpful but mostly restates the core function. There's no mention of pagination or response format, but for a simple reference list this is a minor gap.

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-loaded with the main action, and no redundant phrases. Every sentence adds value: what it does, what it returns, and when to use it.

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?

For a simple, read-only reference tool with one optional parameter fully described in the schemaending no output schema, the description is largely complete. The main missing piece is the exact return structure (e.g., whether it's a flat list or grouped by enum type), but the examples and use case make it clear enough for an agent to call correctly.

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 description covers the only parameter (enum_type) at 100%, including the filter options and the behavior when omitted. The description itself adds no additional parameter detail beyond the general reference-to-field-values context. Since schema coverage is high, 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 lists all valid enum values for ClinicalTrials.gov data fields, using the specific verb 'List' with a specific resource. It also names example enum types (Status, Phase, StudyType, InterventionType) and states its purpose as a reference for building search filters. It doesn't explicitly differentiate from siblings like clinical_trials_field_values, but the core purpose is unambiguous.

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 a clear use case: 'Use as a reference when building search filters or understanding field values.' This tells an agent when to invoke this tool. However, it doesn't explicitly mention alternative tools or when not to use it, leaving some ambiguity relative to similarly-named siblings.

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